-
Notifications
You must be signed in to change notification settings - Fork 12.9k
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
ice: called
Result::unwrap() on an
Err value: Unknown(<SeStr<S, E> as std::ptr::Pointee>::Metadata)
#115628
Comments
build-pass -> ice in nightly-2020-07-31 commit[0] 2020-07-29: Auto merge of #74733 - richkadel:llvm-coverage-map-gen-5, r=tmandry |
probably #73990 ? |
@matthiaskrgr why did you mark this as P-critical if it's a stable-to-stable regression from 2020? |
Minimal: extern "C" fn foo<T: ?Sized + 'static>() -> Option<&'static T> { None } |
its a regression build pass -> ice which is critical according to the rustc dev guide |
According to https://forge.rust-lang.org/compiler/prioritization/priority-levels.html (not the dev guide, which I was confused since the dev guide doesn't really mention criteria for priority):
This is a regression since like 1.47, so I don't think it necessarily needs to block a release to fix 😺 |
Ah sorry that's what i meant, right guess its p high then. 👍 |
WG-prioritization assigning priority (Zulip discussion). @rustbot label -I-prioritize +P-medium |
Rollup merge of rust-lang#115631 - compiler-errors:ctypes-unsized, r=davidtwco Don't ICE when computing ctype's `repr_nullable_ptr` for possibly-unsized ty We may not always be able to compute the layout of a type like `&T` when `T: ?Sized`, even if we're able to estimate its size skeleton. r? davidtwco Fixes rust-lang#115628
Code
Meta
rustc --version --verbose
:Error output
Backtrace
The text was updated successfully, but these errors were encountered: