-
Notifications
You must be signed in to change notification settings - Fork 12.8k
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
Change camel case warning to upper camel case #57346
Conversation
Thanks for the pull request, and welcome! The Rust team is excited to review your changes, and you should hear from @eddyb (or someone else) soon. If any changes to this PR are deemed necessary, please add them as extra commits. This ensures that the reviewer can see what has changed since they last reviewed the code. Due to the way GitHub handles out-of-date commits, this should also make it reasonably obvious what issues have or haven't been addressed. Large or tricky changes may require several passes of review and changes. Please see the contribution instructions for more information. |
The job Click to expand the log.
I'm a bot! I can only do what humans tell me to, so if this was not helpful or you have suggestions for improvements, please ping or otherwise contact |
This looks good so far, but you'll need to make sure the lines aren't longer than 100 characters (e.g. https://github.com/rust-lang/rust/pull/57346/files#diff-a027af56133818b67275f8d2d9c06a40R92). You can run Also, could you squash all the changes into a single commit? r? @varkor |
It would also be convenient for you to squash your commits down to one, given that this is a single conceptual change. Also, avoid merging from master into your branch, use rebase. The line you need to get below 100 chars is |
Ok working on this now, thanks for the feedback and sorry for the delay, VERY VERY busy at work this last week. |
In theory we shouldn't require trusty so long as docker continues to work!
Those tests are directly taken from the comments on the bug reports.
When resolving Fn traits, the compiler failed to take into account overloaded implementations. To resolve this, we inform the trait dispatch code that the arguments will becoming as a tuple of correct arity.
This allows to verify that we handle different types as return types, and that we call the expected functions.
It used to display as just `impl`
There is no type T, such that `T = [T; 2]`, we should not allow this to be circumvented by impl Trait.
Rust structs should be named in upper camel case aka PascalCase. "Upper camel case" was decided upon as the preferred phrase over PascalCase per: rust-lang/rfcs#2389
Ping from triage @tcullum-gpsw: Thanks for your contributions! Do you think you'll be able to get back to this PR? |
ping from triage @tcullum-gpsw Unfortunately we haven't heard from you on this in a while, so I'm closing the PR to keep things tidy. Don't worry though, if you'll have time again in the future please reopen this PR, we'll be happy to review it again! Thanks for taking the time to contribute :) |
Changed 5 files to update from structs having camel case to structs having "upper camel case" as discussed #57319 and rust-lang/rfcs#2389