-
Notifications
You must be signed in to change notification settings - Fork 13.4k
Do not fail evaluation in const blocks #92892
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Do not fail evaluation in const blocks #92892
Conversation
r? @nagisa (rust-highfive has picked a reviewer for you, use r? to override) |
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.
The fix LGTM but I think this needs a test.
r? @fee1-dead @rustbot author: please add a ui test for the issue, in |
Error: Parsing shortcut command in comment failed: ...'bot author' | error: expected end of command at >| ': please a'... Please let |
7ced82c
to
b9a3c32
Compare
@rustbot ready Hah, sorry, added a test last night then forgot to commit it. |
@bors r+ rollup |
📌 Commit b9a3c32 has been approved by |
…askrgr Rollup of 8 pull requests Successful merges: - rust-lang#92747 (Simplification of BigNum::bit_length) - rust-lang#92767 (Use the new language identifier for Rust in the PDB debug format) - rust-lang#92775 (Inline std::os::unix::ffi::OsStringExt methods) - rust-lang#92863 (Remove `&mut` from `io::read_to_string` signature) - rust-lang#92865 (Ignore static lifetimes for GATs outlives lint) - rust-lang#92873 (Generate more precise generator names) - rust-lang#92879 (Add Sync bound to allocator parameter in vec::IntoIter) - rust-lang#92892 (Do not fail evaluation in const blocks) Failed merges: r? `@ghost` `@rustbot` modify labels: rollup
Add `~const` bound test for negative impls Resolves rust-lang#92114 which has been fixed in rust-lang#92892.
Evaluate const blocks with a const param-env, so we properly check
~const
trait bounds.Fixes #92713
(I will fix the poor diagnostics in #92713 and #92712 in a separate PR)
cc @nbdd0121 who wrote the code this PR touches in #89561