Add fast-path for accessing the current thread id #143069

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

Jump to bottom

Open

jsimmons wants to merge 1 commit into rust-lang:master

from jsimmons:current-thread-id-accessor

Open

Add fast-path for accessing the current thread id #143069

jsimmons wants to merge 1 commit into rust-lang:master from jsimmons:current-thread-id-accessor

Conversation

jsimmons

Copy link

Contributor

@jsimmons jsimmons commented Jun 26, 2025

Accessing the thread id is often used in profiling and debugging, as well as some approaches for sound single-threaded access to shared data.

Currently the only way to access the thread id is by first obtaining a handle to the current thread. While this is not exactly slow, it does require an atomic inc-ref and dec-ref operation, as well as the injection of Thread's drop code into the caller.

This publicly exposes the existing fast-path for accessing the current thread id.

Note: I have no idea how these kinds of proposals usually go, but an acp felt overkill for a tiny code change so here we are :)

@jsimmons


 Add fast-path for accessing the current thread id

175584f

Accessing the thread id is often used in profiling and debugging, as
well as some approaches for sound single-threaded access to data.
Currently the only way to access the thread id is by first obtaining a
handle to the current thread. While this is not exactly slow, it does
require an atomic inc-ref and dec-ref operation, as well as the
injection of `Thread`'s drop code into the caller.
This publicly exposes the existing fast-path for accessing the current
thread id.

@rustbot rustbot assigned jhpratt

Jun 26, 2025

@rustbot

Copy link

Collaborator