- Notifications
You must be signed in to change notification settings - Fork153
Use#[expect(...)] instead of#[allow(...)] in some places#1073
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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
base:master
Are you sure you want to change the base?
Uh oh!
There was an error while loading.Please reload this page.
Conversation
Use the #[expect(...)] attribute instead of #[allow(...)] in a bunch ofplaces where we only have the attribute to silence a lint. The formermakes sure that the silenced issue is actually flagged, or prints awarning otherwise.Signed-off-by: Daniel Müller <deso@posteo.net>
This requires Rust |
This pull request is considered stale because it has been open 30 days with no activity. Remove stale label or comment or it will be closed in 5 days. |
This pull request is considered stale because it has been open 30 days with no activity. Remove stale label or comment or it will be closed in 5 days. |
This pull request is considered stale because it has been open 30 days with no activity. Remove stale label or comment or it will be closed in 5 days. |
Closing pull request as it is stale. |
This pull request is considered stale because it has been open 30 days with no activity. Remove stale label or comment or it will be closed in 5 days. |
Use the
#[expect(...)]attribute instead of#[allow(...)]in a bunch of places where we only have the attribute to silence a lint. The former makes sure that the silenced issue is actually flagged, or prints a warning otherwise.