-
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
Migrate rustc_mir_build diagnostics #104417
Conversation
Thanks for the pull request, and welcome! The Rust team is excited to review your changes, and you should hear from @davidtwco (or someone else) soon. Please see the contribution instructions for more information. |
cc @davidtwco, @compiler-errors, @JohnTitor, @estebank, @TaKO8Ki |
This comment was marked as resolved.
This comment was marked as resolved.
You should be able to fix this by using |
This comment has been minimized.
This comment has been minimized.
Ah that's good to know. I've fixed that and rebased. |
} else { | ||
// FIXME: migration of this diagnostic will require list support |
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.
You can try using the list support added in #104047, maybe better as a follow-up so we can land this though.
Apologies for the delay in getting back to this. @bors r |
Migrate rustc_mir_build diagnostics Rebases rust-lang#100854 ~~The remaining issue is how to better resolve rust-lang@72bea68af4ee2a41c44998916f6a789163f12e7d~~ ~~The diagnostic macros seems to generate a broken diagnostic, and I couldn't figure out how to manually format the fluent message, so I hardcoded the format string for now. I'd like pointers to a better fix for this.~~ Also, I'm not 100% sure I didn't mess up a rebase somewhere 🙂 r? `@davidtwco`
☔ The latest upstream changes (presumably #104809) made this pull request unmergeable. Please resolve the merge conflicts. |
Rebased @rustbot ready |
@bors r=davidtwco |
I think this fixes the ice that was hit during rollup, but I'm not sure how to test it locally. |
I think this works on |
@bors r=davidtwco |
☀️ Test successful - checks-actions |
Finished benchmarking commit (35a99ee): comparison URL. Overall result: ❌✅ regressions and improvements - no action needed@rustbot label: -perf-regression Instruction countThis is a highly reliable metric that was used to determine the overall result at the top of this comment.
Max RSS (memory usage)ResultsThis is a less reliable metric that may be of interest but was not used to determine the overall result at the top of this comment.
CyclesThis benchmark run did not return any relevant results for this metric. |
Rebases #100854
The remaining issue is how to better resolve 72bea68The diagnostic macros seems to generate a broken diagnostic, and I couldn't figure out how to manually format the fluent message, so I hardcoded the format string for now. I'd like pointers to a better fix for this.Also, I'm not 100% sure I didn't mess up a rebase somewhere 🙂
r? @davidtwco