Skip to content

Reordering type parameters bounds in trait vs impl causes ICE during trans #6334

Closed
@nikomatsakis

Description

@nikomatsakis

The following test causes an ICE in trans:

// Copyright 2012 The Rust Project Developers. See the COPYRIGHT
// file at the top-level directory of this distribution and at
// http://rust-lang.org/COPYRIGHT.
//
// Licensed under the Apache License, Version 2.0 <LICENSE-APACHE or
// http://www.apache.org/licenses/LICENSE-2.0> or the MIT license
// <LICENSE-MIT or http://opensource.org/licenses/MIT>, at your
// option. This file may not be copied, modified, or distributed
// except according to those terms.

// Tests that everything still compiles and runs fine even when
// we reorder the bounds.

trait A {
    fn a(&self) -> uint;
}

trait B {
    fn b(&self) -> uint;
}

trait C {
    fn combine<T:A+B>(&self, t: &T) -> uint;
}

struct Foo;

impl A for Foo {
    fn a(&self) -> uint { 1 }
}

impl B for Foo {
    fn b(&self) -> uint { 2 }
}

struct Bar;

impl C for Bar {
    // Note below: bounds in impl decl are in reverse order.
    fn combine<T:B+A>(&self, t: &T) -> uint {
        (t.a() * 100) + t.b()
    }
}

fn use_c<S:C, T:B+A>(s: &S, t: &T) -> uint {
    s.combine(t)
}

fn main() {
    let foo = Foo;
    let bar = Bar;
    let r = use_c(&bar, &foo);
    assert_eq!(r, 102);
}

Metadata

Metadata

Assignees

No one assigned

    Labels

    A-codegenArea: Code generationA-trait-systemArea: Trait systemI-ICEIssue: The compiler panicked, giving an Internal Compilation Error (ICE) ❄️

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions