2 ms·
The part about the naming conventions (https://rust-lang.github.io/api-guidelines/naming.html#ad-hoc-conversions-follow-as_-to_-into_-conventions-c-conv https:/
by Zababa 5y ago
The part about the naming conventions (https://rust-lang.github.io/api-guidelines/naming.html#ad-hoc-conversions-follow-as_-to_-into_-conventions-c-conv https://rust-lang.github.io/api-guidelines/naming.html#ad-ho...) reminds me of Elixir's size and length (https://hexdocs.pm/elixir/naming-conventions.html#length-and-size https://hexdocs.pm/elixir/naming-conventions.html#length-and...). I wonder if there is a way to enforce those conventions with a compiler/linter?
- codys 5y agoclippy can be used to check some of these conventions. See https://rust-lang.github.io/rust-clippy/master/#wrong_self_convention https://rust-lang.github.io/rust-clippy/master/#wrong_self_c..., for example. On projects I work on, I include clippy as part of the CI process to check these types of things.