-
Notifications
You must be signed in to change notification settings - Fork 12.9k
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
Better error for normalization errors from parent crates that use #![feature(generic_const_exprs)]
#94440
Conversation
r? @wesleywiser (rust-highfive has picked a reviewer for you, use r? to override) |
r? @lcnr |
This comment has been minimized.
This comment has been minimized.
671b719
to
00b199f
Compare
This comment has been minimized.
This comment has been minimized.
00b199f
to
ae28b6a
Compare
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.
i somewhat dislike generic_const_exprs
infecting layout computation. maybe instead add an else branch for
if infcx.tcx.features().generic_const_exprs { |
where we fatal error if uv
is from an extern crate and has an AbstractConst
? Would prefer something like this here.
@lcnr I considered adding it there instead.. I'll try that! |
@rustbot author |
ae28b6a
to
61de042
Compare
@rustbot ready |
61de042
to
109cdc7
Compare
@rustbot ready |
@bors r+ rollup thanks 👍 |
📌 Commit 109cdc7 has been approved by |
Better error for normalization errors from parent crates that use `#![feature(generic_const_exprs)]` This PR implements a somewhat rudimentary heuristic to suggest using `#![feature(generic_const_exprs)]` in a child crate when a function from a foreign crate (that may have used `#![feature(generic_const_exprs)]`) fails to normalize during codegen. cc: rust-lang#79018 cc: rust-lang#94287
Better error for normalization errors from parent crates that use `#![feature(generic_const_exprs)]` This PR implements a somewhat rudimentary heuristic to suggest using `#![feature(generic_const_exprs)]` in a child crate when a function from a foreign crate (that may have used `#![feature(generic_const_exprs)]`) fails to normalize during codegen. cc: rust-lang#79018 cc: rust-lang#94287
…askrgr Rollup of 8 pull requests Successful merges: - rust-lang#94440 (Better error for normalization errors from parent crates that use `#![feature(generic_const_exprs)]`) - rust-lang#94587 (Document new recommended use of `FromIterator::from_iter`) - rust-lang#94644 (Fix soundness issue in scoped threads.) - rust-lang#94740 (Unify impl blocks by wrapping them into a div) - rust-lang#94753 (Improve rustdoc book) - rust-lang#94796 (Allow `cargo run` instead of `cargo run -p bootstrap`) - rust-lang#94805 (Revert accidental stabilization) - rust-lang#94809 (RustWrapper: add missing include) Failed merges: r? `@ghost` `@rustbot` modify labels: rollup
This PR implements a somewhat rudimentary heuristic to suggest using
#![feature(generic_const_exprs)]
in a child crate when a function from a foreign crate (that may have used#![feature(generic_const_exprs)]
) fails to normalize during codegen.cc: #79018
cc: #94287