-
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
[WIP] rustc_typeck: ensure type alias bounds are implied by the type being well-formed. #54090
Conversation
@bors try (hoping for a crater check run) |
⌛ Trying commit ab3e0d2 with merge 3a2610c2a16575649896925631bf8cec4f4b1961... |
You should be able to start the crater run yourself via the bot, see directions here: https://github.com/rust-lang-nursery/crater/blob/master/docs/bot-usage.md |
The job Click to expand the log.
I'm a bot! I can only do what humans tell me to, so if this was not helpful or you have suggestions for improvements, please ping or otherwise contact |
☀️ Test successful - status-travis |
@craterbot run p=1 start=master#f50b7758f4dc85dc1c5e38258adaa94213ac6ed1 end=try#3a2610c2a16575649896925631bf8cec4f4b1961 cap-lints=warn mode=check-only |
👌 Experiment ℹ️ Crater is a tool to run experiments across parts of the Rust ecosystem. Learn more |
🚧 Experiment ℹ️ Crater is a tool to run experiments across parts of the Rust ecosystem. Learn more |
🎉 Experiment
|
Most of the failures come from diesel, and are probably caused by the fact that this is only one half of the check. There are a few legitimate ones. Overall, this seems like not a dent in the ecosystem. |
About that |
@RalfJung I don't want to keep the |
(you can see above I opened 4 PRs - I want to reuse the |
2409: Don't #[allow(type_alias_bounds)]. r=kvark a=eddyb rust-lang/rust#54090 will fix false positives (not relevant here) and make it an error in the upcoming Rust 2018 edition, which means that if you want to migrate to Rust 2018, it shouldn't be ignored. See also rust-lang/rust#49441 (comment) for the decision and some background. Co-authored-by: Eduard-Mihai Burtescu <edy.burt@gmail.com>
rustc: keep a Span for each predicate in ty::GenericPredicates. This should allow finer-grained diagnostics, including migration suggestions for #54090. (Note that I haven't changed most of the users of `predicates_of` to use the new spans) r? @nikomatsakis
rustc: keep a Span for each predicate in ty::GenericPredicates. This should allow finer-grained diagnostics, including migration suggestions for #54090. (Note that I haven't changed most of the users of `predicates_of` to use the new spans) r? @nikomatsakis
Ping from triage! IIUC, this is waiting on some other PRs to be submitted, so I'm marking this as blocked. |
I'm going to close this PR for now. I do plan to start opening some PRs and issuing warnings, per the plan discussed in #55222 |
NOTE: this is mainly for crater, we'll only emit hard errors on Rust 2018.
This is the second half to a plan outlined in comment on #49441 (see #54033 for the first half).
Fixes #21903 (by disallowing currently unenforceable bounds instead of enforcing them).
This PR includes two hacks: first to not check (usually implied)
T: Sized
bounds, as they're a common source of breakage and would probably be too annoying in practice, and a second to remove some overlap with #54033, so adding missing bounds is not required to test this PR.A decision should be made about the former hack, while the latter is only a temporary convenience.
r? @nikomatsakis