Tobias Bucher 440bf4ded9 crate::io::Result → io::Result in most places ... I don't know why many places refer to the type as `crate::io::Result` when `crate::io` is already imported.		2025-12-29 15:09:48 +01:00
..
builder.rs	crate::io::Result → io::Result in most places	2025-12-29 15:09:48 +01:00
current.rs	std: split up the thread module	2025-11-29 15:59:11 +01:00
functions.rs	std: update broken links in thread module	2025-11-29 15:59:11 +01:00
id.rs	ThreadId generation fallback path: avoid spurious yields	2025-11-30 22:52:28 +01:00
join_handle.rs	std: update references to FromInner etc.	2025-12-15 14:00:37 +01:00
lifecycle.rs	std: update references to FromInner etc.	2025-12-15 14:00:37 +01:00
local.rs	Add documentation guaranteeing global allocator use of TLS	2025-11-28 00:09:12 +01:00
main_thread.rs	std: split up the thread module	2025-11-29 15:59:11 +01:00
mod.rs	std: update broken links in thread module	2025-11-29 15:59:11 +01:00
scoped.rs	crate::io::Result → io::Result in most places	2025-12-29 15:09:48 +01:00
spawnhook.rs	std: split up the thread module	2025-11-29 15:59:11 +01:00
tests.rs	std: split up the thread module	2025-11-29 15:59:11 +01:00
thread.rs	std: update broken links in thread module	2025-11-29 15:59:11 +01:00