JP Simard

You're correct to note that SwiftSyntax is responsible for the bulk of the compilation time. That's also tracked here: https://github.com/apple/swift-syntax/issues/1194 This is why most users should be using pre-built SwiftLint...

How does that compare with running `swiftlint` as installed from Homebrew from your command line?

> The only thing needed is to get the SourceKitten changes in (but haven't been able to get response from @jpsim to get those resolved and merged). Last I checked...

I don't think we're tracking this anywhere, but making `OpeningBraceRule` be configurable by mode (maybe `newline: true` or `mode: same_line`/`mode: new_line`) is fine by me! :+1:

Can you please share the full log output I suspect there's some useful. You can get the full logs by clicking the "Export" button in the Xcode log window

Note that the "never" case already exists as the [Redundant Optional Initialization Rule](https://github.com/realm/SwiftLint/blob/master/Rules.md#redundant-optional-initialization). I'm ok if we want to rename this rule and make it configurable to both cases.

Thanks for the report. It should be possible to check to see if we're in a result builder.

> Perhaps such temporary changes would cause more problems than they're worth though That's my thoughts on this. I suggest you disable the rule with `// swiftlint:disable` comments where you're...

I don't understand what you're trying to do. The `--use-stdin` does not lint a file, it lints the input read via stdin, so there's no path associated to it. For...

@fredpi is SwiftLint's resident configuration expert, maybe he can comment on this?