-
Notifications
You must be signed in to change notification settings - Fork 13.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Allow Numbers After Underscore in Camel Case Types #12986
Comments
I did some searching and could not find any precedence for this. The tools that convert from underscore to camel case either removes numbers or merges them together, which means there is no conventions to write multiple numbers in this style. It is easier to add those exceptions later than removing them. I talked to somebody on the rust-internals IRC channel. One was ok with it (if precedence) and one was against. Nobody was strongly in favor of it, neither am I. Closing. |
Fix pattern field completions not working for unions
…1995 Cache lintcheck binary in ci Always trims ~40s off the `diff` job as it no longer needs to install the rust toolchain or compile lintcheck. Saves a further ~20s for the `base`/`head` jobs when the cache is warm It now uses artifacts for restoring the JSON between jobs as per rust-lang/rust-clippy#10398 (comment), cc `@flip1995` The lintcheck changes are to make `./target/debug/lintcheck` work, running `cargo-clippy`/`clippy-driver` directly doesn't work without `LD_LIBRARY_PATH`/etc being set which is currently being done by `cargo run`. By merging the `--recursive` and normal cases to both go via regular `cargo check` we can have Cargo set up the environment for us r? `@xFrednet` changelog: none
I get this lint on names like:
Suggests allowing numbers after underscore by replacing
with
This function to be put within 'is_camel_case':
Edit: changed to better version suggested by huonw.
The text was updated successfully, but these errors were encountered: