ICE when using += with a struct field with generic type

[MaikKlein]

https://gist.github.com/MaikKlein/5650864

[emberian]

Updated:

struct Vec3<T> {
    x: T,
    y: T,
    z: T
}
impl<T: Add<T,T>+Clone> Vec3<T> {
    fn add(&mut self,v: Vec3<T>){
        self.x += v.x.clone();
        self.y += v.y.clone();
        self.z += v.z.clone();
    }
}
fn main() {
    let mut v1 : Vec3<int> = Vec3{x: 1,y: 1,z: 1,};
    let v2 : Vec3<int> = Vec3{x: 1,y: 1,z: 1,};
    v1.add(v2);
}

yields

foo.rs:8:8: 8:30 error: binary operation + cannot be applied to type `T`
foo.rs:8         self.x += v.x.clone();
                 ^~~~~~~~~~~~~~~~~~~~~~
foo.rs:9:8: 9:30 error: binary operation + cannot be applied to type `T`
foo.rs:9         self.y += v.y.clone();
                 ^~~~~~~~~~~~~~~~~~~~~~
foo.rs:10:8: 10:30 error: binary operation + cannot be applied to type `T`
foo.rs:10         self.z += v.z.clone();
                  ^~~~~~~~~~~~~~~~~~~~~~
error: internal compiler error: no type for node 36: callee_scope v.x.clone() (id=36) in fcx 7fd2bc7f4090

[pnkfelix]

Visited for bug triage email 2013-07-29.

Updated bug title to be more descriptive.

Bug still replicates on rustc 0.8-pre (7b2163d 2013-08-05 00:56:00 -0700)

[huonw]

Triage, still a bug. Minimal example:

struct Foo<T> {
    x: T,
}
impl<T> Foo<T> {
    fn add(&mut self, v: Foo<T>){
        self.x += v.x;
    }
}
fn main() {}

Changing v to just be T and writing self.x += v doesn't show the ICE, but changing it to

    fn add(&self, v: &mut T){
        v += self.x;
    }

does. (Also using + instead of += doesn't ICE; changing the title to be more-r descriptive.)

[luqmana]

Cannot reproduce ICE. It just errors out:

-> % rustc 6738.rs
6738.rs:6:9: 6:22 error: binary assignment operation `+=` cannot be applied to type `T`
6738.rs:6         self.x += v.x;
                  ^~~~~~~~~~~~~
error: aborting due to previous error

With rustc 0.10-pre (6e7f170 2014-03-03 05:51:38 -0800). Flagging as needs-test.