-
Notifications
You must be signed in to change notification settings - Fork 1.8k
Suggest naming types before using explicit type names #14996
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
Conversation
|
r? @Alexendoo rustbot has assigned @Alexendoo. Use |
|
r? clippy |
blyxyas
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What do you think about this improvement? If the transmute argument is something like x, it doesn't make that much sense calling it "the origin type" and not just mentioning x
87bd829 to
77eda2d
Compare
Good idea. I've credited you in the commit message as well. |
77eda2d to
1e85800
Compare
blyxyas
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Small stylistic change and this is ready for merge.
`missing_transmute_annotations` will suggest naming the origin and destination types if they do not have explicit names already. Co-authored-by: Alejandra González <[email protected]>
1e85800 to
a7ff2b0
Compare
blyxyas
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, thanks! ❤️
missing_transmute_annotationswill suggest naming the origin and destination types if they do not have explicit names already.changelog: [
missing_transmute_annotations]: suggest giving origin and destination types a name in order to ascribe thetransmutecallFixes #14984