Mercurial > crates > nonstick
view src/libpam/mod.rs @ 141:a508a69c068a
Remove a lot of Results from functions.
Many functions are documented to only return failing Results when given
improper inputs or when there is a memory allocation failure (which
can be verified by looking at the source). In cases where we know our
input is correct, we don't need to check for memory allocation errors
for the same reason that Rust doesn't do so when you, e.g., create a
new Vec.
author | Paul Fisher <paul@pfish.zone> |
---|---|
date | Sat, 05 Jul 2025 17:16:56 -0400 |
parents | 80c07e5ab22f |
children | 56b559b7ecea |
line wrap: on
line source
//! The implementation of the PAM interface that wraps `libpam`. //! //! While you're going to want to write PAM modules and applications against //! the interfaces in [the `handle` module](crate::handle) for testability, //! this is (probably) what will be used behind the scenes. #![allow(dead_code)] mod answer; mod conversation; mod environ; mod handle; mod memory; mod module; mod question; #[doc(inline)] pub use handle::{OwnedLibPamHandle, RawPamHandle};