rust/library/std/src/sys/thread_local, branch try

Rollup merge of #141455 - joboet:tls_exhaustion_abort, r=tgross35

2025-06-03T19:53:36+00:00

std: abort the process on failure to allocate a TLS key The panic machinery uses TLS, so panicking if no TLS keys are left can lead to infinite recursion (see https://github.com/rust-lang/rust/issues/140798#issuecomment-2872307377). Rather than having separate logic for the panic count and the thread name, just always abort the process if a TLS key allocation fails. This also has the benefit of aligning the key-based TLS implementation with the documentation, which does not mention that a panic could also occur because of resource exhaustion.

Address review comments.

2025-05-30T10:14:27+00:00

When replacing an old value we may not drop it in place

2025-05-28T15:53:14+00:00

Add same unsafe bound on get_or_init_slow

2025-05-28T15:10:50+00:00

Do not panic, maintain old behavior

2025-05-28T14:56:26+00:00

Improve safety comment, double-drop is not relevant here

2025-05-28T12:51:52+00:00

Do not move thread-locals before dropping

2025-05-28T12:39:51+00:00

std: abort the process on failure to allocate a TLS key

2025-05-23T16:00:09+00:00

The panic machinery uses TLS, so panicking if no TLS keys are left can lead to infinite recursion (see https://github.com/rust-lang/rust/issues/140798#issuecomment-2872307377). Rather than having separate logic for the panic count and the thread name, just always abort the process if a TLS key allocation fails. This also has the benefit of aligning the key-based TLS implementation with the documentation, which does not mention that a panic could also occur because of resource exhaustion.

docs: fix typos

2025-05-22T14:47:36+00:00

use generic Atomic type where possible

2025-04-26T23:18:08+00:00

in core/alloc/std only for now, and ignoring test files Co-authored-by: Pavel Grigorenko