-
Notifications
You must be signed in to change notification settings - Fork 12.8k
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 4 pull requests #113114
Rollup of 4 pull requests #113114
Conversation
The only regression is one ambiguity in the new trait solver, having to do with two param-env candidates that may apply. I think this is fine, since the error message already kinda sucks.
…s, r=davidtwco Validate fluent variable references in tests Closes rust-lang#101109 Under `cfg(test)`, the `fluent_messages` macro will emit a list of variables referenced by each message and its attributes. The derive attribute will now emit a `#[test]` that checks that each referenced variable exists in the structure it's applied to.
…its, r=lcnr More `ImplSource` nits Even more clean-ups, I'll put this up in parallel with the `select_in_new_trait_solver` PR. r? `@lcnr`
…-in-head, r=notriddle,fmease Fix invalid HTML DIV tag used in HEAD Fixes rust-lang#113067. The issue also nicely explains the whole problem. r? `@notriddle`
…piler-errors add myself to review for t-types stuff I think this is how the triagebot stuff works 😅 should mean that `r? types` can now assign me
@bors p=4 |
@bors r+ 🙃 |
⌛ Testing commit 3798eda with merge d2270c70ca93f41912e04bebe45ecaebc8274716... |
#111269 already merged? bors should prevent things like that. |
@bors r- |
☀️ Try build successful - checks-actions |
1 similar comment
☀️ Try build successful - checks-actions |
Successful merges:
ImplSource
nits #112867 (MoreImplSource
nits)r? @ghost
@rustbot modify labels: rollup
Create a similar rollup