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

pedantic clippy cleanup #760

Closed
spacejam opened this issue Aug 15, 2019 · 4 comments
Closed

pedantic clippy cleanup #760

spacejam opened this issue Aug 15, 2019 · 4 comments

Comments

@spacejam
Copy link
Owner

There are many issues when running cargo clippy -- -W clippy::pedantic from the root. Most of them are quite easy to fix (please ignore cyclometric complexity issues).

Please help us clean some of them up! Even a single one is helpful!

@sitano
Copy link
Collaborator

sitano commented Aug 31, 2019

do you think pedantic naming worth it? (pid <-> lid, lsn <-> len are forbidden)

@spacejam
Copy link
Owner Author

spacejam commented Sep 2, 2019

@sitano Personally I'm fine with these abbreviations because I've seen them every day for the last 3 years, but I think for other people they might not be very descriptive. pid would probably be better as page_id, lid would probably be better as log_id. But lsn and len though are both kind of idiomatic (LSN in the database world is pretty ubiquitous). So I think that renaming is not worth it for lsn and len, but pid and lid could probably be less confusing for newcomers to the codebase.

@sitano
Copy link
Collaborator

sitano commented Sep 2, 2019

@spacejam thats exactly what I did) agree that all that idiomatic stuff does not make sense to rename. I thought that even pid does not worth it.

@sitano
Copy link
Collaborator

sitano commented Sep 3, 2019

as far as I saw, there is nothing to fix there anymore. only integer ops related stuff left, naming with module and use of default - all this unfixable. maybe its worth creating another execution string for clippy with all current warns that left allowed, because there is no chance find anything useful behind this wall of integer devisions and precision losts.

@spacejam spacejam unpinned this issue Oct 11, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants