-
Notifications
You must be signed in to change notification settings - Fork 12.7k
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
Rollup of 7 pull requests #68319
Rollup of 7 pull requests #68319
Conversation
…in_patterns, r=centril Don't warn about snake case for field puns. Closes rust-lang#66362.
Update rustc-guide r? @ghost CC: @rust-lang/wg-learning
…ef, r=oli-obk Fix deref impl typedef Fixes rust-lang#35295. r? @kinnison
…lan-DPC Clean up E0198 explanation r? @Dylan-DPC
…ntril Add regression test for integer literals in generic arguments in where clauses Closes rust-lang#67753.
Stop treating `FalseEdges` and `FalseUnwind` as having semantic value for const eval This change does not expose loops or conditions to stable const fns because we check those at the HIR level and in the regular const validity checks. cc @ecstatic-morse r? @eddyb
…lan-DPC Clean up E0199 explanation r? @Dylan-DPC
@bors r+ p=7 rollup=never |
📌 Commit b7af138 has been approved by |
⌛ Testing commit b7af138 with merge 2351560c592ec5a375aeaf50d083661fbd506f00... |
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 |
💔 Test failed - checks-azure |
Looks spurious... |
Successful merges:
FalseEdges
andFalseUnwind
as having semantic value for const eval #68314 (Stop treatingFalseEdges
andFalseUnwind
as having semantic value for const eval)Failed merges:
r? @ghost