Skip to content

Commit

Permalink
Fix FAILPOINTS variable name in docs, and lints (#76)
Browse files Browse the repository at this point in the history
Signed-off-by: Martin Pool <mbp@sourcefrog.net>
  • Loading branch information
sourcefrog committed Feb 28, 2024
1 parent 5bc95a1 commit 00dd175
Showing 1 changed file with 2 additions and 3 deletions.
5 changes: 2 additions & 3 deletions src/lib.rs
Original file line number Diff line number Diff line change
Expand Up @@ -72,7 +72,7 @@
//!
//! ## Usage in tests
//!
//! The previous example triggers a fail point by modifying the `FAILPOINT`
//! The previous example triggers a fail point by modifying the `FAILPOINTS`
//! environment variable. In practice, you'll often want to trigger fail points
//! programmatically, in unit tests.
//! Fail points are global resources, and Rust tests run in parallel,
Expand All @@ -81,7 +81,7 @@
//!
//! Here's a basic pattern for writing unit tests tests with fail points:
//!
//! ```rust
//! ```rust,no_run
//! use fail::{fail_point, FailScenario};
//!
//! fn do_fallible_work() {
Expand Down Expand Up @@ -244,7 +244,6 @@ impl Debug for SyncCallback {
}

impl PartialEq for SyncCallback {
#[allow(clippy::vtable_address_comparisons)]
fn eq(&self, other: &Self) -> bool {
Arc::ptr_eq(&self.0, &other.0)
}
Expand Down

0 comments on commit 00dd175

Please sign in to comment.