-
Notifications
You must be signed in to change notification settings - Fork 1.7k
clippy::uninit_vec
raises ICE
#12032
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
Comments
@rustbot claim |
So I have "triaged" the issue to: https://github.com/rust-lang/rust-clippy/blob/master/clippy_utils/src/ty.rs#L612-L616 pub fn is_uninit_value_valid_for_ty<'tcx>(cx: &LateContext<'tcx>, ty: Ty<'tcx>) -> bool {
cx.tcx
.check_validity_requirement((ValidityRequirement::Uninit, cx.param_env.and(ty)))
.unwrap_or_else(|_| is_uninit_value_valid_for_ty_fallback(cx, ty))
} More specifically cx.tcx
.check_validity_requirement(_) when given:
but I am not sure how to move from here. |
Maybe ask the compiler team directly? |
The code still raises ICE in the latest nightly clippy. Why close it? |
This is not a clippy issue, but a rustc issue. The corresponding issue has been created in rustc. |
Summary
This code raises ICE. If
clippy::uninit_vec
is skipped, it does not raise ICE any more.Version
Error output
Backtrace
The text was updated successfully, but these errors were encountered: