Open workingjubilee opened 1 week ago
r? @TaKO8Ki
rustbot has assigned @TaKO8Ki. They will have a look at your PR within the next two weeks and either review your PR or reassign to another reviewer.
Use r?
to explicitly pick a reviewer
Some changes occurred in compiler/rustc_codegen_cranelift
cc @bjorn3
These commits modify compiler targets. (See the Target Tier Policy.)
https://github.com/rust-lang/rust/pull/125127 was opened which suggests "always" and "never" as other options. I think adding "always" to this is fine if there's no objection from the reviewer (who also seconded the MCP) but I don't believe we need more options for saying "no" because "never" is even more confusing than "no" or "off" (because it is strong enough it might come off as "force frame pointers to NEVER HAPPEN!!!" which is not at all what will occur).
The job mingw-check-tidy
failed! Check out the build log: (web) (plain)
Why don't we already support this...?
Suggested impl for https://github.com/rust-lang/compiler-team/issues/744