Skip to content

Conversation

@ISSOtm
Copy link
Contributor

@ISSOtm ISSOtm commented Jun 26, 2022

Also remove #[allow(clippy::*)]s where possible

src/utils/fs.rs Outdated
} else {
fs::remove_file(item)?;
}
for item in fs::read_dir(dir)?.flatten() {
Copy link
Contributor

Choose a reason for hiding this comment

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

I find this harder to read, can it be reverted?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Clippy says otherwise, fwiw.

I personally prefer flatten() due to removing one level of indentation and a couple of lines.

Copy link
Contributor

Choose a reason for hiding this comment

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

I don't agree with quite a few clippy lints. If it were about lines or indentation, then several of these other changes should not be included because they add more lines and indentation. In this case, it is not as clear what is being flattened as the types are obscured. By checking for Ok(…), it is clear that it is explicitly ignoring errors.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Fair point, I'll revert it then.

src/book/book.rs Outdated
/// [`iter()`]: #method.iter
/// [`for_each_mut()`]: #method.for_each_mut
#[derive(Debug, Clone, Default, PartialEq, Serialize, Deserialize)]
#[non_exhaustive]
Copy link
Contributor

Choose a reason for hiding this comment

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

This is a breaking change and cannot be done in a point release.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I'll revert it, then; but, should the lint be kept so we can remember for the next major release, or should it be suppressed?

Copy link
Contributor

Choose a reason for hiding this comment

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

I filed #1835 to track considering it in a point release. I don't have much of an opinion on allowing it, as I don't use clippy. I'm not particularly happy with lots of allow(clippy) stuff, but if you'd like to add it, that would be fine.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I agree allows should be kept to a minimum, hence why I also tried removing existing ones.

If it's being tracked, then I think it's fine to live with the warning—I certainly could, I was more concerned about Clippy's two denys in the current codebase.

Also remove `allow(clippy::*)`s where possible
Copy link
Contributor

@ehuss ehuss left a comment

Choose a reason for hiding this comment

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

Thanks!

@ehuss ehuss merged commit 4cf005d into rust-lang:master Jun 27, 2022
@ISSOtm ISSOtm deleted the clippy branch June 27, 2022 21:29
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