-
Notifications
You must be signed in to change notification settings - Fork 431
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
rust: kernel: cleanup unsafe
in unsafe fn
s warnings (E0133
)
#340
Comments
Doesn't that belong in a separate PR? Because if we add |
The intention of having |
Well, it is "just" comments. The idea is that we take the time to write and review the
Indeed, these need cleanup too. The plan has been to add a |
Sounds like a plan! |
For |
@ojeda is there merit in carrying out this work in a dedicated feature branch? Silencing the unsafe warnings involves placing new But in the meantime, other contributors will run into >100 warnings when they build their PRs. This may inhibit further development. It was certainly problematic for me while working on #335. Moving the warning fixes to a dedicated branch would allow parallelisation, which would be beneficial to all? At the end of the week you can just merge the feature branch into |
It is a fair point, specially since we already have people working on downstream repos. Let's do the following: I will send a PR to add all the Then I will add a feature branch with the |
Great idea! I'm 100% on board with that. |
See #340 Signed-off-by: Sven Van Asbroeck <[email protected]>
See Rust-for-Linux#340 Signed-off-by: Sven Van Asbroeck <[email protected]>
We enabled the warnings in #339 and we would like to move it to hard error, so we need to clean them up.
Any PR that cleans some of these is very much appreciated -- no need to do them all at once. Do not forget to add the relevant
// SAFETY
comment!Current set (116 warnings)
The text was updated successfully, but these errors were encountered: