fix: missing_transmute_annotations should not contain fn name in suggestion - #17611
fix: missing_transmute_annotations should not contain fn name in suggestion#17611GTimothy wants to merge 2 commits into
Conversation
|
Thanks for the pull request, and welcome! You should hear from one of our reviewers after this PR gets at least 2 reviews from the community. Please see the contribution instructions for more information. |
|
Should I squash or keep in two commits? |
|
r? @Jarcho rustbot has assigned @Jarcho for the project review. Use Why was this reviewer chosen?The reviewer was selected based on:
|
|
@GTimothy could you please reorder the commits so that the actual change comes last? That would make it easier to revert just that commit, if need be. (This is also the reason why keeping drive-by clean-ups as a separate commit is preferred, and much appreciated) |
|
Reminder, once the PR becomes ready for a review, use |
00d1c2a to
e07efdf
Compare
|
@rustbot ready |
There was a problem hiding this comment.
Personally I consider with_types_for_suggestion to be a somewhat ugly hack... But I guess we could use this fix for now, and whoever comes up with a better solution than with_types_for_suggestion in the future could change this lint accordingly.
git nit: your second commit now contains the messages from both commits 😅
e07efdf to
a48f4f2
Compare
It felt weird to use :) but it was the solution to the issue you referenced in the original issue.
I did some git gymnastics, splitting the commit before being able to reorder without conflict and squashed but did not cleanup after, fixed now |
fixes #15839:
missing_transmute_annotationscontaining fn name in suggestion (such asmain) which fails to resolvechangelog:[
missing_transmute_annotations]: remove function names from the suggestion