lithium 1.0.4

//! Lightweight exceptions.
//!
//! Lithium provides a custom exception mechanism as an alternative to Rust panics. Compared to Rust
//! panics, this mechanism is allocation-free, avoids indirections and RTTI, and is hence faster, if
//! less applicable.
//!
//! On nightly, Lithium is more than 2x faster than Rust panics on common `Result`-like usecases.
//! See the [benchmark](https://github.com/iex-rs/lithium/blob/master/benches/bench.rs).
//!
//!
//! # Usage
//!
//! Throw an exception with [`throw`], catch it with [`catch`] or the more low-level [`intercept`].
//! Unlike with Rust panics, non-[`Send`] and non-`'static` types can be used soundly.
//!
//! Using the `panic = "abort"` strategy breaks Lithium; avoid doing that.
//!
//! For interop, all crates that depend on Lithium need to use the same version:
//!
//! ```toml
//! [dependencies]
//! lithium = "1"
//! ```
//!
//! If you break either of these two requirements, cargo will scream at you.
//!
//!
//! # Platform support
//!
//! On stable Rust, Lithium uses the built-in panic mechanism, tweaking it to increase performance
//! just a little bit.
//!
//! On nightly Rust, Lithium uses a custom mechanism on the following targets:
//!
//! |Target             |Implementation |Performance                                  |
//! |-------------------|---------------|---------------------------------------------|
//! |Linux, macOS       |Itanium EH ABI |2.5x faster than panics                      |
//! |Windows (MSVC ABI) |SEH            |1.5x faster than panics                      |
//! |Windows (GNU ABI)  |Itanium EH ABI |2.5x faster than panics, but slower than MSVC|
//! |Emscripten (old EH)|C++ exceptions |2x faster than panics                        |
//! |Emscripten (new EH)|Wasm exceptions|2.5x faster than panics                      |
//! |WASI               |Itanium EH ABI |2.5x faster than panics                      |
//!
//! Lithium strives to support all targets that Rust panics support. If Lithium does not work
//! correctly on such a target, please [open an issue](https://github.com/iex-rs/lithium/issues/).
//!
//! On nightly, Lithium can work without `std` on certain platforms that expose native thread
//! locals and link in an Itanium-style unwinder. Such situations are best handled on a case-by-case
//! basis: [open an issue](https://github.com/iex-rs/lithium/issues/) if you would like to see
//! support for a certain `std`-less target.
//!
//!
//! # Safety
//!
//! Exceptions lack dynamic typing information. For soundness, the thrown and caught types must
//! match exactly. Note that the functions are generic, and if the type is inferred wrong, UB will
//! happen. Use turbofish to avoid this pitfall.
//!
//! The matching types requirement only applies to exceptions that aren't caught inside the
//! [`catch`]/[`intercept`] callback. For example, this is sound:
//!
//! ```rust
//! use lithium::{catch, throw};
//!
//! struct A;
//! struct B;
//!
//! unsafe {
//!     let _ = catch::<_, A>(|| {
//!         let _ = catch::<_, B>(|| throw(B));
//!         throw(A);
//!     });
//! }
//! ```
//!
//! The responsibility of upholding this safety requirement is split between the throwing and the
//! catching functions. All throwing functions must be `unsafe`, listing "only caught by type `E`"
//! as a safety requirement. All catching functions that take a user-supplied callback must be
//! `unsafe` too, listing "callback only throws type `E`" as a safety requirement.
//!
//! Although seemingly redundant, this enables safe abstractions over exceptions when both the
//! throwing and the catching functions are provided by one crate. As long as the exception types
//! used by the crate match, all safe user-supplied callbacks are sound to call, because safe
//! callbacks can only interact with exceptions in an isolated manner.

#![no_std]
#![cfg_attr(all(thread_local = "attribute"), feature(thread_local))]
#![cfg_attr(
    any(backend = "itanium", backend = "seh", backend = "emscripten"),
    expect(
        internal_features,
        reason = "Can't do anything about core::intrinsics::catch_unwind yet",
    )
)]
#![cfg_attr(
    any(backend = "itanium", backend = "seh", backend = "emscripten"),
    feature(core_intrinsics, rustc_attrs)
)]
#![cfg_attr(backend = "seh", feature(fn_ptr_trait, std_internals))]
#![cfg_attr(
    all(backend = "itanium", target_arch = "wasm32"),
    feature(wasm_exception_handling_intrinsics)
)]
#![deny(unsafe_op_in_unsafe_fn)]
#![warn(
    clippy::cargo,
    clippy::pedantic,
    clippy::alloc_instead_of_core,
    clippy::allow_attributes_without_reason,
    clippy::arithmetic_side_effects,
    clippy::as_underscore,
    clippy::assertions_on_result_states,
    clippy::clone_on_ref_ptr,
    clippy::decimal_literal_representation,
    clippy::default_numeric_fallback,
    clippy::deref_by_slicing,
    clippy::else_if_without_else,
    clippy::empty_drop,
    clippy::empty_enum_variants_with_brackets,
    clippy::empty_structs_with_brackets,
    clippy::exhaustive_enums,
    clippy::exhaustive_structs,
    clippy::fn_to_numeric_cast_any,
    clippy::format_push_string,
    clippy::infinite_loop,
    clippy::inline_asm_x86_att_syntax,
    clippy::mem_forget, // use ManuallyDrop instead
    clippy::missing_assert_message,
    clippy::missing_const_for_fn,
    clippy::missing_inline_in_public_items,
    clippy::mixed_read_write_in_expression,
    clippy::multiple_unsafe_ops_per_block,
    clippy::mutex_atomic,
    clippy::needless_raw_strings,
    clippy::pub_without_shorthand,
    clippy::rc_buffer,
    clippy::rc_mutex,
    clippy::redundant_type_annotations,
    clippy::rest_pat_in_fully_bound_structs,
    clippy::same_name_method,
    clippy::self_named_module_files,
    clippy::semicolon_inside_block,
    clippy::separated_literal_suffix,
    clippy::shadow_unrelated,
    clippy::std_instead_of_alloc,
    clippy::std_instead_of_core,
    clippy::string_lit_chars_any,
    clippy::string_to_string,
    clippy::tests_outside_test_module,
    clippy::try_err,
    clippy::undocumented_unsafe_blocks,
    clippy::unnecessary_safety_comment,
    clippy::unnecessary_safety_doc,
    clippy::unnecessary_self_imports,
    clippy::unneeded_field_pattern,
    clippy::unused_result_ok,
    clippy::wildcard_enum_match_arm,
)]
#![allow(
    clippy::inline_always,
    reason = "I'm not an idiot, this is a result of benchmarking/profiling"
)]

#[cfg(panic = "abort")]
compile_error!("Using Lithium with panic = \"abort\" is unsupported");

#[cfg(any(abort = "std", backend = "panic", thread_local = "std", test))]
extern crate std;

extern crate alloc;

mod api;
mod backend;

#[cfg(any(backend = "itanium", backend = "emscripten", backend = "panic"))]
mod heterogeneous_stack;
#[cfg(any(backend = "itanium", backend = "emscripten", backend = "panic"))]
mod stacked_exceptions;

#[cfg(any(backend = "itanium", backend = "seh", backend = "emscripten"))]
mod intrinsic;

pub use api::{catch, intercept, throw, InFlightException};

/// Abort the process with a message.
///
/// If `std` is available, this also outputs a message to stderr before aborting.
#[cfg(any(backend = "itanium", backend = "seh", backend = "emscripten"))]
#[cold]
#[inline(never)]
fn abort(message: &str) -> ! {
    #[cfg(abort = "std")]
    {
        use std::io::Write;
        let _ = std::io::stderr().write_all(message.as_bytes());
        std::process::abort();
    }

    // This is a nightly-only method, but all three backends this is enabled under require nightly
    // anyway, so this is no big deal.
    #[cfg(not(abort = "std"))]
    {
        let _ = message;
        core::intrinsics::abort();
    }
}