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

chore: fix clippy warnings #15944

Merged
merged 1 commit into from
Sep 19, 2022

Conversation

bnoordhuis
Copy link
Contributor

Stop allowing clippy::derive-partial-eq-without-eq and fix warnings about deriving PartialEq without also deriving Eq.

In one case I removed the PartialEq because it a) wasn't necessary, and b) sketchy because it was comparing floating point numbers.

IMO, that's a good argument for enforcing the lint rule, because it would most likely have been caught during review if it had been enabled.

Stop allowing clippy::derive-partial-eq-without-eq and fix warnings
about deriving PartialEq without also deriving Eq.

In one case I removed the PartialEq because it a) wasn't necessary,
and b) sketchy because it was comparing floating point numbers.

IMO, that's a good argument for enforcing the lint rule, because it
would most likely have been caught during review if it had been enabled.
Copy link
Member

@dsherret dsherret left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM. This should be enabled.

@bnoordhuis bnoordhuis merged commit b1b418b into denoland:main Sep 19, 2022
@bnoordhuis bnoordhuis deleted the derive-partial-eq-without-eq branch September 19, 2022 08:25
dsherret pushed a commit that referenced this pull request Sep 22, 2022
Stop allowing clippy::derive-partial-eq-without-eq and fix warnings
about deriving PartialEq without also deriving Eq.

In one case I removed the PartialEq because it a) wasn't necessary,
and b) sketchy because it was comparing floating point numbers.

IMO, that's a good argument for enforcing the lint rule, because it
would most likely have been caught during review if it had been enabled.
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

2 participants