fc28a2a506
The developer experience for panics is to provide the backtrace and exit the program. When running under debugger, that might be improved by breaking into the debugger once the code panics thus enabling the developer to examine the program state at the exact time when the code panicked. Let the developer catch the panic in the debugger if it is attached. If the debugger is not attached, nothing changes. Providing this feature inside the standard library facilitates better debugging experience. Validated under Windows, Linux, macOS 14.6, and FreeBSD 13.3..14.1.
24 lines
526 B
Rust
24 lines
526 B
Rust
#![allow(unsafe_op_in_unsafe_fn)]
|
|
|
|
/// The PAL (platform abstraction layer) contains platform-specific abstractions
|
|
/// for implementing the features in the other submodules, e.g. UNIX file
|
|
/// descriptors.
|
|
mod pal;
|
|
|
|
mod alloc;
|
|
mod personality;
|
|
|
|
pub mod anonymous_pipe;
|
|
pub mod backtrace;
|
|
pub mod cmath;
|
|
pub mod dbg;
|
|
pub mod exit_guard;
|
|
pub mod os_str;
|
|
pub mod path;
|
|
pub mod sync;
|
|
pub mod thread_local;
|
|
|
|
// FIXME(117276): remove this, move feature implementations into individual
|
|
// submodules.
|
|
pub use pal::*;
|