Tracking issue for std::thread::ThreadId

[aldanor]

Update description

Tracking issue for std::thread::ThreadId. Points to consider when stabilizing:

• Implementation of a mutex + u64, unconditional panic if space is exhausted
• Various traits on ThreadId, including Copy

Original report

Not sure if it can be considered as bug but it sure cripples the existing threading API (e.g., makes it harder for a thread to identify itself or store/pass its identity).

// it could also be nice if Thread was able to return a unique integer id() (or hash itself?..).

[murarth]

I'd also like to have Eq implemented for Thread. Would a PR be accepted to this effect or would it require an RFC?

[remram44]

I'd very much like some kind of thread id, I'm pretty sure every Thread implementation around gives numeric ids (Python has a string name much like Rust but also offers Thread.ident, "a nonzero integer").

[frewsxcv]

FYI, here's the associated issue in the RFCs repo: rust-lang/rfcs#1435

[ticki]

I think it would be fitting to implement Hash, like std::mem::Discriminant, which doesn't expose an actual value either.