Skip to content
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

using resources as explicit type argument yields ICE #1916

Closed
nikomatsakis opened this issue Mar 1, 2012 · 0 comments
Closed

using resources as explicit type argument yields ICE #1916

nikomatsakis opened this issue Mar 1, 2012 · 0 comments

Comments

@nikomatsakis
Copy link
Contributor

I have no idea what's going on here, but it has something to do with using a resource as the type argument to foo():

resource r(_i: uint) {
}

fn foo<T>() {
}

fn main() {
    foo::<r>();
}

yields the following

Running /usr/local/bin/rustc:
rust: upcall fail 'option none', ../src/libcore/option.rs:34
0   librustrt.dylib                     0x00000001074229f9 __morestack + 9�
error: internal compiler error unexpected failure
note: The compiler hit an unexpected failure path. This is a bug. Try running with RUST_LOG=rustc=0,::rt::backtrace to get further details and report the results to github.com/mozilla/rust/issues
rust: upcall fail 'explicit failure', ../src/comp/driver/rustc.rs:176
0   librustrt.dylib                     0x00000001074229f9 __morestack + 9�
rust: domain main @0x7fb80301dc00 root task failed
@marijnh marijnh closed this as completed in 0398456 Mar 1, 2012
flip1995 pushed a commit to flip1995/rust that referenced this issue Aug 11, 2022
flip1995 pushed a commit to flip1995/rust that referenced this issue Aug 11, 2022
…Frednet

Rename `logic_bug` to `overly_complex_bool_expr`

Closes rust-lang#1916

changelog: Rename `logic_bug` to [`overly_complex_bool_expr`]
celinval added a commit to celinval/rust-dev that referenced this issue Jun 4, 2024
Ignore clang-format error for now. I'm also printing the version to see if that's the culprit of the new issue we are seeing.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants