Danny Mösch

Would you please provide examples?

You explicitly mention Linux. Did you try the same on macOS?

In principle, it is possible to implement something like you propose as an [analyzer rule](https://github.com/realm/SwiftLint#analyze) which requires the full set of compile commands and takes considerably more time to run...

> Hello. Is it possible to add new password to store after successful registration on site in browser? It's not possible at the moment. Auto-fill works, but password entries have...

Have you tried the shortcut? What do you want to change?

> It's more than a year and currently using stable 0.52.2 (bottled) version. (installed via brew) Still can see the warning in my environment. > > ``` > var aPointPosition:...

This is a known shortcoming of this rule that we need to accept. It's impossible to get that right on the syntax-level (where SwiftLint operates on). It would need to...

> I just enabled `xct_specific_matcher`, and came across this. True that we cannot always determine if `b` is optional, but in cases like `XCTAssertTrue(someVar?.x)`, shouldn't we be able to catch...

> Is this not problematic because there's no guarantees that types that implement `==` also conform to `Equatable`. Tuples come to mind, where you can write `XCTAssert(foo == bar)` but...

I've implemented parts for this rule in #4911. As mentioned there, what's missing ~~are two cases~~ is one case: * ~~Weakly captured `self` with explicit unwrapping according to [SE-0365](https://github.com/apple/swift-evolution/blob/main/proposals/0365-implicit-self-weak-capture.md)~~ *...