static-analysis

New Issue Checklist

• Handle new UIEdgeInsets.zero case

Describe the bug

The use of prefer_zero_over_explicit_init doesn't cover UIEdgeInsets.zero case.

For example we have next code

extension UIApplication {
    static var safeAreaInsets: UIEdgeInsets {
        UIWindow.key?.safeAreaInsets ?? UIEdgeInsets(top: 0, left: 0, bottom: 0, right: 0) // Here should 

Describe the bug
A clear and concise description of what the bug is.
Metavariables do not work for object reference in Scala

To Reproduce
Steps to reproduce the behavior, ideally a link to https://semgrep.dev:
The link is attached https://semgrep.dev/s/zojz

Expected behavior
A clear and concise description of what you expected to happen.
Based on the link, there should be t

Many repositories need to fix, so please help if you like.

If you could help, it would be helpful if you could comment before starting the work not to overlapping.

Fix example

Run exit command after lint.

echo '::group:: Running golangci-lint with reviewdog 🐶 ...'
go

Oh, I thought I already added negative-int but I guess not. It should be easy to do if someone wants to add that

Originally posted by @orklah in vimeo/psalm#8060 (comment)

Should be trivial to add in Atomic::create (see how positive-int is handled there).

We'll probably want

• non-negative-int
• negative-int
• non-positive-int

just

Context

BooleanPropertyNaming considers naming of properties, while technically these const vals are properties, they also have a different naming convention and I have a feeling they rarely start with IS_ prefix.

Expected Behavior of the rule

I propose to exclude const from this check fully.

object WidgetPreferences { // Detekt: or a companion object

	/**
	 * Us