-
Notifications
You must be signed in to change notification settings - Fork 13.3k
Rollup of 5 pull requests #59582
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 5 pull requests #59582
Conversation
Remove unnecessary comment
This commit extends the existing generic re-ordering diagnostic to include any bounds on the generic parameter, thus producing correct suggestions.
This commit updates the generic parameter re-ordering diagnostic to only mention const generics if the feature is enabled.
It is possible to create malformed LLVM IR given variadic arguments that are aggregate types. This occurs due to improper tracking of the current argument in the functions list of arguments.
…ths-libstd, r=oli-obk libstd: deny(elided_lifetimes_in_paths) r? @oli-obk
…i-obk Mention `no merge policy` in the CONTRIBUTING guide Issue: rust-lang#59233
Include bounds in generic re-ordering diagnostic Fixes rust-lang#59508. r? @estebank cc @varkor
…ing, r=Centril Distinguish message for external macros depending on error level fixes rust-lang#57716 (I picked you because assigned to this issue.) r? @estebank
Fix LLVM IR generated for C-variadic arguments It is possible to create malformed LLVM IR given variadic arguments that are aggregate types. This occurs due to improper tracking of the current argument in the functions list of arguments. Fixes: rust-lang#58881
@bors r+ p=5 |
📌 Commit 3d308ee has been approved by |
⌛ Testing commit 3d308ee with merge 9eb52ff643a2f2da49b1240e0d5ee2782c6b1128... |
💔 Test failed - checks-travis |
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 |
Successful merges:
no merge policy
in the CONTRIBUTING guide #59234 (Mentionno merge policy
in the CONTRIBUTING guide)Failed merges:
r? @ghost