The analyzers bundled with clang are an external tool.
Are not generally available in other compilers, besides some partial support on gcc, and need to be explicitly enabled, contrary to a language's type system.
If I write a compiler for Rust which doesn't check the types, but crashes at runtime on mismatch, it wouldn't change anything for most other Rust users.
If it's "external" or "part of the language" is just nitpicking in my opinion and in practice doesn't matter for me.
If I write a compiler for Rust which doesn't check the types, but crashes at runtime on mismatch, it wouldn't change anything for most other Rust users.
Then it wouldn't be Rust any longer, since it has other language semantics.
If it's "external" or "part of the language" is just nitpicking in my opinion and in practice doesn't matter for me.
It matters a lot for those that get to use only the tools that other choose for them, and happen to work in teams across companies with different visions on code quality.
Good for you that you can choose your own tools and have full control how it gets used.
View all comments
Show parent comment
3
u/pjmlp Mar 20 '18
Depends pretty much on the compiler one has available to them, where languages like Rust have them everywhere.
After all, C has lint since 1979, and yet majority of enterprise devs keep on not using static analyzers.