-
Notifications
You must be signed in to change notification settings - Fork 12.7k
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
Forbid generic parameters in anon consts inside of type defaults #74487
Conversation
This finishes the implementation of the required limitation discussed in https://rust-lang.zulipchat.com/#narrow/stream/131828-t-compiler/topic/type.20of.20const.20parameters/near/203406561 |
@bors r+ |
📌 Commit 5cc40f3c091c9f057571641ca2fa04947409b5cc has been approved by |
⌛ Testing commit 5cc40f3c091c9f057571641ca2fa04947409b5cc with merge 0d528478bb6829d402606cc81f78d091cb186a32... |
💔 Test failed - checks-actions |
5cc40f3
to
952fd0c
Compare
Rebased and updated the affected tests. @bors r=varkor |
📌 Commit 952fd0c has been approved by |
…arth Rollup of 4 pull requests Successful merges: - rust-lang#73858 (Make more primitive integer methods const) - rust-lang#74487 (Forbid generic parameters in anon consts inside of type defaults) - rust-lang#74803 (rustbuild: fix bad usage of UNIX exec() in rustc wrapper) - rust-lang#74822 (More ensure stack to avoid segfault with increased `recursion_limit`) Failed merges: r? @ghost
Emit a resolution error for
struct Foo<T, U = [u8; std::mem::size_of::<T>()]>
.We are unable to support this with the way
ty::Generics
is currently used,so let's just forbid it entirely for now.
Fixes some ICE on stable, e.g.
r? @varkor @eddyb