@WG-prioritization/alerts issue #75982 has been requested for prioritization.
I-nominated
?ICE's instead of erroring, P-medium
?
Fails on nightly consistently (just tried with nightly 1.48), would it make sense to raise it to a P-high
or perhaps it's not so worrying?
Issue #75982's prioritization request has been removed.
apiraino said:
Fails on nightly consistently (just tried with nightly 1.48), would it make sense to raise it to a
P-high
or perhaps it's not so worrying?
it's a thing that should fail but it's giving an ICE so it's not so worrying IMO
agree with @LeSeulArtichaut here :)
Hey, the author of safer-ffi
here. There is an actual ICE regression here: my crate has an example / test that relies on the proc_macros
feature to be enabled, hence it seemingly "failing" on 1.45.2
when it actually doesn't.
That is, cargo +1.45.2 check --all-targets --features proc_macros
does not fail.
And yet cargo +nightly check --all-targets --features proc_macros
does (with my nightly being 1.49.0
)
@WG-prioritization/alerts issue #75982 has been requested for prioritization.
I-nominated
?I think P-high or P-critical; it's working code -> ICE
thanks @Daniel Henry-Mantilla for catching it!
probably P-high
Just applied P-high
. Triagebot hasn't picked up on it though, I assume because of the GitHub incident :/
Issue #75982's prioritization request has been removed.