-
Notifications
You must be signed in to change notification settings - Fork 12.6k
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 #125079
Rollup of 5 pull requests #125079
Commits on Jan 14, 2024
-
Configuration menu - View commit details
-
Copy full SHA for 4333fb0 - Browse repository at this point
Copy the full SHA 4333fb0View commit details
Commits on May 7, 2024
-
Configuration menu - View commit details
-
Copy full SHA for b39ef8b - Browse repository at this point
Copy the full SHA b39ef8bView commit details
Commits on May 10, 2024
-
Configuration menu - View commit details
-
Copy full SHA for 4fde241 - Browse repository at this point
Copy the full SHA 4fde241View commit details -
Configuration menu - View commit details
-
Copy full SHA for c565a0a - Browse repository at this point
Copy the full SHA c565a0aView commit details -
Configuration menu - View commit details
-
Copy full SHA for 03d9e84 - Browse repository at this point
Copy the full SHA 03d9e84View commit details
Commits on May 13, 2024
-
Don't call
env::set_var
inrustc_driver::install_ice_hook
Modifying an environment variable would make the function unsafe to call.
Configuration menu - View commit details
-
Copy full SHA for b98b8d7 - Browse repository at this point
Copy the full SHA b98b8d7View commit details -
style-guide: Format single associated type
where
clauses on the sam……e line In particular, lifetime-generic associated types often have a `where Self: 'a` bound, which we can format on the same line.
Configuration menu - View commit details
-
Copy full SHA for 3742a4b - Browse repository at this point
Copy the full SHA 3742a4bView commit details -
style-guide: Give a second example for associated type formatting
Show an example that has bounds.
Configuration menu - View commit details
-
Copy full SHA for 2f20bb4 - Browse repository at this point
Copy the full SHA 2f20bb4View commit details -
Configuration menu - View commit details
-
Copy full SHA for 2af29af - Browse repository at this point
Copy the full SHA 2af29afView commit details -
Configuration menu - View commit details
-
Copy full SHA for 9ff777b - Browse repository at this point
Copy the full SHA 9ff777bView commit details -
Reword formatting for where clauses
Suggested-by: Caleb Cartwright <[email protected]>
Configuration menu - View commit details
-
Copy full SHA for 163b1a6 - Browse repository at this point
Copy the full SHA 163b1a6View commit details -
Rollup merge of rust-lang#119515 - joshtriplett:style-guide-gat-where…
…-clause-same-line, r=compiler-errors style-guide: Format single associated type `where` clauses on the same line In particular, lifetime-generic associated types often have a `where Self: 'a` bound, which we can format on the same line.
Configuration menu - View commit details
-
Copy full SHA for b568cc2 - Browse repository at this point
Copy the full SHA b568cc2View commit details -
Rollup merge of rust-lang#119959 - fmease:triagebot-prioritization-al…
…ert-label, r=apiraino [meta] Clarify prioritization alert Apparently, there used to exist the label <kbd>I-nominated</kbd> judging from this entry: https://github.com/rust-lang/rust/blob/8847bda592d940ae1f34d87d8cacdc09a9f787fa/triagebot.toml#L393 Since it was replaced with individual team labels, I think it makes sense to update the prioritization alert. Of course, it's not super important since the members of WG-prioritization already know that. This is just cleanup. r? apiraino or wg-prioritization
Configuration menu - View commit details
-
Copy full SHA for a7b9536 - Browse repository at this point
Copy the full SHA a7b9536View commit details -
Rollup merge of rust-lang#124532 - lcnr:elaborate-coherence, r=compil…
…er-errors elaborate obligations in coherence The following test currently does not pass coherence: ```rust trait Super {} trait Sub<T>: Super {} trait Overlap<T> {} impl<T, U: Sub<T>> Overlap<T> for U {} impl<T> Overlap<T> for () {} fn main() {} ``` We check whether `(): Sub<?t>` holds. This stalls with ambiguity as downstream crates may add an impl for `(): Sub<Local>`. However, its super trait bound `(): Super` cannot be implemented downstream, so this one is known not to hold. By elaborating the bounds in the implicit negative overlap check, this now compiles. This is necessary to prevent breakage from enabling `-Znext-solver=coherence` (rust-lang#121848), see tests/ui/coherence/super-traits/super-trait-knowable-2.rs for more details. r? `@compiler-errors`
Configuration menu - View commit details
-
Copy full SHA for 176741b - Browse repository at this point
Copy the full SHA 176741bView commit details -
Rollup merge of rust-lang#124844 - compiler-errors:shadow-probe, r=lcnr
Use a proper probe for shadowing impl r? lcnr
Configuration menu - View commit details
-
Copy full SHA for 3ea4fdf - Browse repository at this point
Copy the full SHA 3ea4fdfView commit details -
Rollup merge of rust-lang#125063 - tbu-:pr_set_ice_hook_env, r=michae…
…lwoerister Don't call `env::set_var` in `rustc_driver::install_ice_hook` Modifying an environment variable would make the function unsafe to call.
Configuration menu - View commit details
-
Copy full SHA for 8e1dc65 - Browse repository at this point
Copy the full SHA 8e1dc65View commit details