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

Dead code removal #101

Merged
merged 1 commit into from
Jan 27, 2025
Merged

Dead code removal #101

merged 1 commit into from
Jan 27, 2025

Conversation

srhb
Copy link
Contributor

@srhb srhb commented Jan 23, 2025

No description provided.

cafkafk added a commit to eza-community/eza that referenced this pull request Jan 23, 2025
Apparently, upstream rust decided to change the behavior of dead/unused
code detection in a way that causes a lot of false positives.

For some (yet known) reason, this only hit on the windows build, but
I've confirmed that these are indeed false positives, and removing this
"dead code" breaks the build.

Frustratingly, we only hit this to fix *another issue*[1] with upstream
rust... And this litters our code with directives where we "allow
unused" that isn't unused.

I coindicentally also saw this at dayjob today[2], and yes, this is
real, so we'll just have to do it.

Refs: [1] rust-lang/rust@e69f14b
Refs: [2] DBCDK/faythe#101
Refs: rust-lang/rust#88900
Refs: #1342

Signed-off-by: Christina Sørensen <ces@fem.gg>
cafkafk added a commit to eza-community/eza that referenced this pull request Jan 23, 2025
Apparently, upstream rust decided to change the behavior of dead/unused
code detection in a way that causes a lot of false positives.

For some (yet known) reason, this only hit on the windows build, but
I've confirmed that these are indeed false positives, and removing this
"dead code" breaks the build.

Frustratingly, we only hit this to fix *another issue*[1] with upstream
rust... And this litters our code with directives where we "allow
unused" that isn't unused.

I coindicentally also saw this at dayjob today[2], and yes, this is
real, so we'll just have to do it.

Refs: [1] rust-lang/rust@e69f14b
Refs: [2] DBCDK/faythe#101
Refs: rust-lang/rust#88900
Refs: #1342

Signed-off-by: Christina Sørensen <ces@fem.gg>
cafkafk added a commit to eza-community/eza that referenced this pull request Jan 23, 2025
Apparently, upstream rust decided to change the behavior of dead/unused
code detection in a way that causes a lot of false positives.

For some (yet known) reason, this only hit on the windows build, but
I've confirmed that these are indeed false positives, and removing this
"dead code" breaks the build.

Frustratingly, we only hit this to fix *another issue*[1] with upstream
rust... And this litters our code with directives where we "allow
unused" that isn't unused.

I coindicentally also saw this at dayjob today[2], and yes, this is
real, so we'll just have to do it.

Refs: [1] rust-lang/rust@e69f14b
Refs: [2] DBCDK/faythe#101
Refs: rust-lang/rust#88900
Refs: #1342

Signed-off-by: Christina Sørensen <ces@fem.gg>
Leaves in one:

```
warning: field `0` is never read
   --> src/issuer.rs:246:28
    |
246 |     NoIpsForResolversFound(&'l String),
    |     ---------------------- ^^^^^^^^^^
    |     |
    |     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
    |
246 |     NoIpsForResolversFound(()),
    |
```

That one should probably be dealt with after the next nixpkgs bump,
because it'll start affecting every field that is only read via derived
Debug traits. That seems to warrant some discussion.
@srhb srhb force-pushed the dead-code-removal branch from 983dcd3 to a0df172 Compare January 24, 2025 08:47
@srhb srhb marked this pull request as ready for review January 24, 2025 08:48
@srhb
Copy link
Contributor Author

srhb commented Jan 24, 2025

Not draft. Not dealing with the final dead_code warning due to the upcoming clippy MR + nixpkgs update which will bring in a lot more of them.

@srhb
Copy link
Contributor Author

srhb commented Jan 24, 2025

~/platform/faythe dead-code-removal
nix-shell-env ❯ cargo build
   Compiling faythe v0.1.0 (/home/sarah/platform/faythe)
warning: field `0` is never read
   --> src/issuer.rs:246:28
    |
246 |     NoIpsForResolversFound(&'l String),
    |     ---------------------- ^^^^^^^^^^
    |     |
    |     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
    |
246 |     NoIpsForResolversFound(()),
    |                            ~~

@0z13 0z13 merged commit a2cda04 into main Jan 27, 2025
1 check passed
@cafkafk cafkafk deleted the dead-code-removal branch January 28, 2025 04:48
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.

2 participants