Stream: t-compiler/wg-prioritization/alerts

Topic: I-prioritize #27970 Does getaddrinfo need to take the ENV l…

triagebot (Nov 12 2020 at 14:28, on Zulip):

@WG-prioritization/alerts issue #27970 has been requested for prioritization.


Hameer Abbasi (Nov 12 2020 at 14:32, on Zulip):

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?

apiraino (Nov 18 2020 at 11:08, on Zulip):

I'm not entirely sure about this one. This comment and this comment seems to imply (or perhaps I am misinterpreting) that this is unsafe but documented.

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

Santiago Pastorino (Nov 18 2020 at 20:14, on Zulip):

bump, unprioritized

Santiago Pastorino (Nov 18 2020 at 20:40, on Zulip):

I'm not even sure what to do with this one

lcnr (Nov 18 2020 at 20:47, on Zulip):

Afaict the unsafety is only caused when interacting with extern code, so the standard library on its own is sound

Santiago Pastorino (Nov 18 2020 at 20:48, on Zulip):

@lcnr yep

Santiago Pastorino (Nov 18 2020 at 20:48, on Zulip):

so unsure :)

lcnr (Nov 18 2020 at 20:48, on Zulip):

though it does seem like this happens at least somewhat frequently

lcnr (Nov 18 2020 at 20:49, on Zulip):

or much rather, there are unsound apis out there where the unsoundness is hard to trigger

lcnr (Nov 18 2020 at 20:50, on Zulip):

idk, let's just slap P-medium on it and hope it doesn't end up biting us?

triagebot (Nov 18 2020 at 21:12, on Zulip):

Issue #27970's prioritization request has been removed.

Last update: Apr 15 2021 at 02:30UTC