Skip to content

using resources as explicit type argument yields ICE #1916

Closed
@nikomatsakis

Description

@nikomatsakis

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions