-
Notifications
You must be signed in to change notification settings - Fork 13.1k
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
Const eval doesn't normalize opaques in FnDef correctly #103507
Comments
Just putting this here so it shows up in searches. ICE
Full ICE output
|
Fixed on the latest nightly, marking as E-needs-test (or, feel free to close if we have a sufficient regression test) |
test already exists impl-trait/normalize-tait-in-const.rs |
This is a "known-bug" test pointing here. So the issue isn't fixed, I think? |
That said, the code currently doesn't make any sense since |
…er-errors const traits: remove some known-bug that do not seem to make sense These tests were made to point to rust-lang#103507 in rust-lang#114134; I think that was a mistake: that issue is about a rather specific problem, and most tests marked as known-bug in that PR are pointing at rust-lang#110395 which makes more sense. Of the 4 tests that still point to rust-lang#103507: - One is [the original test](https://github.com/rust-lang/rust/blob/20882608529a969bd878ad787cf0038716c021df/tests/ui/impl-trait/normalize-tait-in-const.rs). It still fails to compile, though currently for unrelated reasons (`~const Fn` is not valid as that is not a const trait). I made it point at rust-lang#110395 like all the other tests that were disabled when the previous const trait impl was removed. - One is being fixed in rust-lang#135423 - The other two are fixed in this PR The errors we are getting here are not great but they do look correct? FWIW there are still a whole lot of tests mentioning rust-lang#110395 despite that issue being closed... I hope someone is tracking that.^^ r? `@compiler-errors`
Rollup merge of rust-lang#135523 - RalfJung:wrong-known-bug, r=compiler-errors const traits: remove some known-bug that do not seem to make sense These tests were made to point to rust-lang#103507 in rust-lang#114134; I think that was a mistake: that issue is about a rather specific problem, and most tests marked as known-bug in that PR are pointing at rust-lang#110395 which makes more sense. Of the 4 tests that still point to rust-lang#103507: - One is [the original test](https://github.com/rust-lang/rust/blob/20882608529a969bd878ad787cf0038716c021df/tests/ui/impl-trait/normalize-tait-in-const.rs). It still fails to compile, though currently for unrelated reasons (`~const Fn` is not valid as that is not a const trait). I made it point at rust-lang#110395 like all the other tests that were disabled when the previous const trait impl was removed. - One is being fixed in rust-lang#135423 - The other two are fixed in this PR The errors we are getting here are not great but they do look correct? FWIW there are still a whole lot of tests mentioning rust-lang#110395 despite that issue being closed... I hope someone is tracking that.^^ r? `@compiler-errors`
This won't be easy to fix, but filing a bug just so I can track it in a
// known-bug
issue. This was found out of an attempt to replicate rust-lang/miri#2433 in a UI test.The text was updated successfully, but these errors were encountered: