Skip to content

Check clippy::pedantic lints #100

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

Closed
hug-dev opened this issue Feb 4, 2020 · 2 comments
Closed

Check clippy::pedantic lints #100

hug-dev opened this issue Feb 4, 2020 · 2 comments
Labels
enhancement New feature or request

Comments

@hug-dev
Copy link
Member

hug-dev commented Feb 4, 2020

Activating these lints should improve the quality of code but would necessitate lots of changes amoung our crates. See #91

@hug-dev hug-dev added the enhancement New feature or request label Feb 4, 2020
@ionut-arm
Copy link
Member

Should make sure that the docs are kept up to date, e.g. any changes happening to "The BackEndHandler" in interfaces_and_dataflow.md in Parsec book, in terms of naming operations.

@hug-dev
Copy link
Member Author

hug-dev commented Mar 16, 2020

Some of those lints are useful for example when a component name contains its module name (cf) but some others generate too much noise (cf) and would take long to differentiate between false positives and true positives. Closing this issue for now as this is not an absolute requirement.
It is good to execute from time to time though, locally.

@hug-dev hug-dev closed this as completed Mar 16, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants