-
Notifications
You must be signed in to change notification settings - Fork 13.1k
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: cfi: encode_ty: unexpected 'CoroutineWitness'
#122705
Comments
This comment was marked as outdated.
This comment was marked as outdated.
oh does it now? interesting. |
@maurer: This doesn't change the way that #![feature(async_closure)]
#[inline(never)]
fn foo<T>(x: T) {}
fn main() {
let a = async move |a: i32, b: i32| {};
foo(a);
} Not sure why we're not just encoding the parent args for closures and coroutine-closures. I'll put up a PR. @rustbot claim |
Yes, you're right, we need to be able to encode these. |
Well @rcvalle just pinged me and said he may have a PR that already addresses this, so I guess I'll wait for him to comment. If not, I'll put up a fix for this in a few days since I'm the expert on |
Fix rust-lang#122705 by adding support for encoding `ty:CoroutineClosure`.
Fix rust-lang#122705 by adding support for encoding `ty:CoroutineClosure`.
Fix rust-lang#122705 by adding support for encoding `ty:CoroutineClosure`.
Fix rust-lang#122705 by adding support for encoding `ty:CoroutineClosure`.
Fix rust-lang#122705 by adding support for encoding `ty:CoroutineClosure`.
Fix rust-lang#122705 by adding support for encoding `ty:CoroutineClosure`.
Fix rust-lang#122705 by adding support for encoding `ty:CoroutineClosure`.
Fix rust-lang#122705 by adding support for encoding `ty:CoroutineClosure`.
Fix rust-lang#122705 by adding support for encoding `ty:CoroutineClosure`.
auto-reduced (treereduce-rust):
original code
original:
Version information
Command:
/home/matthias/.rustup/toolchains/master/bin/rustc --edition=2021 --cap-lints=warn -Zsanitizer=cfi -Ccodegen-units=1 -Clto
Program output
The text was updated successfully, but these errors were encountered: