-
Notifications
You must be signed in to change notification settings - Fork 12.8k
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
It's not about types or consts, but the lack of regions #102651
Conversation
Some changes occurred to the CTFE / Miri engine cc @rust-lang/miri Some changes occurred in const_evaluatable.rs cc @lcnr Some changes occurred in src/tools/clippy cc @rust-lang/clippy |
r? @fee1-dead (rust-highfive has picked a reviewer for you, use r? to override) |
📌 Commit d8883422555aa8d73971791dea6cbc8bd0d3be4e has been approved by It is now in the queue for this repository. |
☔ The latest upstream changes (presumably #102622) made this pull request unmergeable. Please resolve the merge conflicts. |
d888342
to
c7b6ebd
Compare
@bors r=lcnr |
…iaskrgr Rollup of 6 pull requests Successful merges: - rust-lang#102241 (Package `rust-docs-json` into nightly components (take 3)) - rust-lang#102488 (Check generic argument compatibility when projecting assoc ty) - rust-lang#102647 (Only allow ~const bounds for traits with #[const_trait]) - rust-lang#102648 (Add test for rust-lang#102605) - rust-lang#102651 (It's not about types or consts, but the lack of regions) - rust-lang#102653 (resolve instance: missing value to `delay_span_bug`) Failed merges: r? `@ghost` `@rustbot` modify labels: rollup
pulled out of #101900 which adds a fourth kind of non-lifetime generic parameter, and the naming of these methods would get ridiculous.