clang-tidy vs SwiftLint
clang-tidy
clang.llvm.orgSwiftLint
realm.github.ioSide by side
| Figure | clang-tidy | SwiftLint |
|---|---|---|
| Price from | Free | Free |
| Free plan | Yes | Yes |
| Free trial | — | — |
| Open source | — | — |
| Windows | — | Yes |
| macOS | — | Yes |
| Linux | Yes | Yes |
| Plans published | 1 | 1 |
| Spec score · Linters | 8.5 (#4) | 8.0 (#11) |
| Configuration | Checks can be selected with comma-separated positive and negative globs, and configuration can be read from a .clang-tidy file. | File inclusions and exclusions can be configured in a `.swiftlint.yml` configuration file. |
| License | The LLVM project states that its code is licensed under the Apache 2.0 License with LLVM exceptions. | The GitHub repository identifies SwiftLint as MIT licensed. |
| Purpose | clang-tidy is a Clang-based C++ linter for diagnosing and fixing typical programming errors, including style violations, interface misuse, and bugs detectable by static analysis. | SwiftLint enforces Swift style and conventions based on rules generally accepted by the Swift community. |
Plans
In their own words
clang-tidy
clang-tidy has no write-up on Specifiction yet; its figures are above.
SwiftLint
SwiftLint is a free, MIT-licensed tool that checks Swift source against style rules and conventions accepted by the Swift community. It includes more than 200 built-in rules, with opt-in rules disabled by default. A project can set active rules, included and excluded paths, and rule settings in a `.swiftlint.yml` file. SwiftLint can automatically correct some violations, overwriting affected files, and its command line supports linting, analysis, baselines, rule listings, and multiple reporters. Documented integrations include Xcode and Swift Package Manager plugins, pre-commit, Fastlane, Docker, Visual Studio Code, and MegaLinter. Installation choices include package managers, prebuilt packages, and source builds. Releases include macOS, Windows, and Linux binaries. SwiftLint is intended for valid, compilable source, and non-compiling code may produce unexpected results, especially when autocorrecting. Analyzer rules are considerably slower than lint rules. The project is maintained by volunteers, and the maintainers describe it as non-commercial.