Skip to content

Fix FAILPOINTS variable name in docs, and lints #76

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 4 commits into from
Feb 28, 2024
Merged

Fix FAILPOINTS variable name in docs, and lints #76

Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
83c0687
Fix typo'd env var name in docs
sourcefrog Jan 2, 2024
3747b3a
Update lint name
sourcefrog Jan 2, 2024
a12a859
Mark doctest no_run
sourcefrog Jan 2, 2024
b0e8a05
Lint suppression is no longer needed
sourcefrog Feb 27, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 2 additions & 3 deletions src/lib.rs
View file
Open in desktop
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