//! Among these features, `ctru-rs` also automatically includes functionality to properly integrate the Rust `std` with the console's operating system,
//! Among these features, [`ctru-rs`](crate) also automatically includes functionality to properly integrate the Rust `std` with the console's operating system,
//! which the developer would otherwise need to implement manually.
//! which the developer would otherwise need to implement manually.
//!
//!
//! # Usage
//! # Usage
@ -53,7 +53,7 @@ macro_rules! from_impl {
};
};
}
}
/// Activate the custom `ctru-rs` panic handler.
/// Activate the custom [`ctru-rs`](crate) panic handler.
///
///
/// With this implementation, the main thread will stop and try to print debug info to an available [`Console`](console::Console).
/// With this implementation, the main thread will stop and try to print debug info to an available [`Console`](console::Console).
/// In case it fails to find an active [`Console`](console::Console) the program will just exit.
/// In case it fails to find an active [`Console`](console::Console) the program will just exit.
//! Most of the 3DS console's functionalities (when writing user-land homebrew) are accessible via services,
//! Most of the 3DS console's functionalities (when writing user-land homebrew) are accessible via services,
//! which need to be initialized before accessing any particular feature.
//! which need to be initialized before accessing any particular feature.
//!
//!
//! To ensure safety while using the underlying services, `ctru-rs` leverages Rust's lifetime model.
//! To ensure safety while using the underlying services, [`ctru-rs`](crate) leverages Rust's lifetime model.
//! After initializing the handle for a specific service (e.g. [`Apt`](apt::Apt)) the service will be accessible as long as there is at least one handle "alive".
//! After initializing the handle for a specific service (e.g. [`Apt`](apt::Apt)) the service will be accessible as long as there is at least one handle "alive".
//! As such, handles should be dropped *after* the use of a specific service. This is particularly important for services which are necessary for functionality
//! As such, handles should be dropped *after* the use of a specific service. This is particularly important for services which are necessary for functionality
//! "outside" their associated methods, such as [`RomFS`](romfs::RomFS), which creates an accessible virtual filesystem, or [`Soc`](soc::Soc),
//! "outside" their associated methods, such as [`RomFS`](romfs::RomFS), which creates an accessible virtual filesystem, or [`Soc`](soc::Soc),
//! which enables all network communications via sockets.
//! which enables all network communications via sockets.
//!
//!
//! In `ctru-rs` some services only allow a single handle to be created at a time, to ensure a safe and controlled environment.
//! In [`ctru-rs`](crate) some services only allow a single handle to be created at a time, to ensure a safe and controlled environment.