@WG-prioritization/alerts issue #27970 has been requested for prioritization.
Oh this one is tricky. On the one hand, multithreading unsoundness. On the other, back-compat. Is there a history of which one we prefer over the other?
What should or could be done on a "T-libs" level or rather in the implementing crates? If the crate uses
localtime_r bypasses the safeguard set by the Rust library (again, this is my understanding).
I am more inclined to maybe
I-nominate this for a discussion
I'm not even sure what to do with this one
Afaict the unsafety is only caused when interacting with extern code, so the standard library on its own is sound
so unsure :)
though it does seem like this happens at least somewhat frequently
or much rather, there are unsound apis out there where the unsoundness is hard to trigger
idk, let's just slap
P-medium on it and hope it doesn't end up biting us?
Issue #27970's prioritization request has been removed.