-
Notifications
You must be signed in to change notification settings - Fork 1.7k
Implement BeginPanic
handling in const eval
#16938
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
Conversation
a03632f
to
6f6a6d5
Compare
I pushed a fix to the minicore fixture which changes the failure of one of the tests |
There were some more issues in the minicore definition (it was written with signatures in mind only so some functions were just lacking bodies etc), now both tests are running into execution limits (probably executing |
Instead of using `core::fmt::format` to format panic messages, which may in turn panic too and cause recursive panics and other messy things, redirect `panic_fmt` to `const_panic_fmt` like CTFE, which in turn goes to `panic_display` and does the things normally. See the tests for the full call stack.
14a75f6
to
4303fdf
Compare
Found another issue, now we actually run into trying to interpret |
4303fdf
to
a9140e1
Compare
|
Previously, |
bb1acb4
to
4426142
Compare
BeginPanic
handling in const eval
@bors r+ |
Implement `BeginPanic` handling in const eval for #16935, needs some figuring out of how to write these tests correctly
💔 Test failed - checks-actions |
598a053
to
7f3b84b
Compare
@bors r+ |
Implement `BeginPanic` handling in const eval for #16935, needs some figuring out of how to write these tests correctly
💔 Test failed - checks-actions |
7f3b84b
to
25e65c1
Compare
25e65c1
to
3b9a2af
Compare
@bors r+ |
☀️ Test successful - checks-actions |
thanks for continuing this, i completely forgot about it 💀 |
for #16935, needs some figuring out of how to write these tests correctly