-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
lint against MaybeUninit::uninit().assume_init()
#4479
Conversation
dfa9cdf
to
d56186b
Compare
r? @flip1995 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM overall. Just a small NIT.
4d3a9c9
to
83eccd2
Compare
For now, this is a "Don't do this" lint. Working with uninitialized values is so complex that I cannot come up with an easy suggestion that would be sound in all cases. @flip1995 r? |
Yeah I did some reading on this topic yesterday. A suggestion that applies in general is probably not possible. Since Clippy broke on the latest rustc master and there wasn't a rustup yet, we have to wait on merging this. cc rust-lang/rust#63561 |
83eccd2
to
b01f2d1
Compare
Thanks! @bors r+ |
📌 Commit b01f2d1 has been approved by |
lint against `MaybeUninit::uninit().assume_init()` changelog: add `uninit_assumed_init` lint This fixes #4272
☀️ Test successful - checks-travis, status-appveyor |
changelog: add
uninit_assumed_init
lintThis fixes #4272