rust - https://github.com/rust-lang/rust

Age	Commit message (Collapse)	Author	Lines
2025-08-06	Print thread ID in panic message if thread name is unknown	Trevor Gross	-1/+1
	`panic!` does not print any identifying information for threads that are unnamed. However, in many cases, the thread ID can be determined. This changes the panic message from something like this: thread '<unnamed>' panicked at src/main.rs:3:5: explicit panic To something like this: thread '<unnamed>' (0xff9bf) panicked at src/main.rs:3:5: explicit panic Stack overflow messages are updated as well. This change applies to both named and unnamed threads. The ID printed is the OS integer thread ID rather than the Rust thread ID, which should also be what debuggers print.
2025-01-01	Try to write the panic message with a single `write_all` call	John Kåre Alsaker	-0/+1

2024-11-30	bless tests for changed library path	Ralf Jung	-1/+1

2024-08-02	Bless tests	bjorn3	-1/+1

2023-07-29	Fix tests.	Mara Bos	-1/+2

2023-07-26	Regression test `println!()` panic message on `ErrorKind::BrokenPipe`	Martin Nordholts	-0/+2
	No existing test failed if the [`panic!()`][1] of the `println!()` family of functions was removed, or if its message was changed. So add such a test. [1] https://github.com/rust-lang/rust/blob/104f4300cfddbd956e32820ef202a732f06ec848/library/std/src/io/stdio.rs#L1007-L1009