Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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
Fix exceeding bitshifts not emitting for assoc. consts (properly this time, I swear!) #71663
Fix exceeding bitshifts not emitting for assoc. consts (properly this time, I swear!) #71663
Changes from all commits
14d90de
326d38f
e66e37c
bc7b714
6b413d9
2887d79
5b1d600
894a83d
656ab76
eca1478
9c898d6
9459b37
cb96d41
425a99f
65c36f6
f1d778f
8175c4c
8304739
bd18ad4
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
Isn't it more of a whitelist? Unexpected errors will bubble up to the root and cause ICEs.
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.
This is great. :D
I think my one complaint is that using curly braces to delemit parameters is a bit odd. We don't write
format_args!{ "{:?}", some_failure }
either. But I don't have a better proposal off the top of my head either... @oli-obk any ideas?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.
I can't come up with a nicer syntax off the top of my head. Parens would definitely look worse:
I think it's fine as it is.
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.
Okay, let's go with curly braces then.
Should we replace
expected
by@expected
or so to more clearly mark it as a keyword? Not sure what the usual macro conventions are, this is certainly something I have seen before.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.
I think it's standing out enough by the definitely not-legal-rust syntax. But I wouldn't mind an additional
@
if you think that makes it clearer.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.
Okay, let's go with this for now, we can always change it later.
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.
Wow this is advanced macro magic, cool stuff.