Skip to content
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.

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

Work around dead_code warning in flock implementation #253

Merged
merged 1 commit into from
Jan 6, 2024
Merged

Conversation

dtolnay
Copy link
Owner

@dtolnay dtolnay commented Jan 6, 2024

Warning is new in nightly-2024-01-06 due to rust-lang/rust#118297.

warning: field `0` is never read
  --> src/flock.rs:22:12
   |
22 |     Locked(MutexGuard<'static, ()>),
   |     ------ ^^^^^^^^^^^^^^^^^^^^^^^
   |     |
   |     field in this variant
   |
   = note: `#[warn(dead_code)]` on by default
help: consider changing the field to be of unit type to suppress this warning while preserving the field numbering, or remove the field
   |
22 |     Locked(()),
   |            ~~

    warning: field `0` is never read
      --> src/flock.rs:22:12
       |
    22 |     Locked(MutexGuard<'static, ()>),
       |     ------ ^^^^^^^^^^^^^^^^^^^^^^^
       |     |
       |     field in this variant
       |
       = note: `#[warn(dead_code)]` on by default
    help: consider changing the field to be of unit type to suppress this warning while preserving the field numbering, or remove the field
       |
    22 |     Locked(()),
       |            ~~
@dtolnay dtolnay merged commit 0321a01 into master Jan 6, 2024
20 checks passed
@dtolnay dtolnay deleted the deadflock branch January 6, 2024 02:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant