auto merge of #13333 : Ryman/rust/improve_incompatible_type_error, r=alexcrichton

This can be a frustrating error message, ideally we should print the signature mismatch, but hinting that it's a trait incompatibility helps tracking root cause. Also beefed up the testcases for this.

Ideally we would print the signature mismatch in the error helper?
This commit is contained in:
bors 2014-04-05 08:41:32 -07:00
commit 94a055c729
2 changed files with 35 additions and 4 deletions

View File

@ -923,7 +923,7 @@ fn compare_impl_method(tcx: &ty::ctxt,
result::Err(ref terr) => {
tcx.sess.span_err(
impl_m_span,
format!("method `{}` has an incompatible type: {}",
format!("method `{}` has an incompatible type for trait: {}",
token::get_ident(trait_m.ident),
ty::type_err_to_str(tcx, terr)));
ty::note_and_explain_type_err(tcx, terr);

View File

@ -13,14 +13,29 @@
// (In this case the mul method should take &f64 and not f64)
// See: #11450
struct Vec1 {
x: f64
}
// Expecting ref in input signature
impl Mul<f64, Vec1> for Vec1 {
fn mul(&self, s: f64) -> Vec1 {
//~^ ERROR: method `mul` has an incompatible type for trait: expected &-ptr but found f64
Vec1 {
x: self.x * s
}
}
}
struct Vec2 {
x: f64,
y: f64
}
// Wrong type parameter ordering
impl Mul<Vec2, f64> for Vec2 {
fn mul(&self, s: f64) -> Vec2 {
//~^ ERROR: method `mul` has an incompatible type: expected &-ptr but found f64
//~^ ERROR: method `mul` has an incompatible type for trait: expected &-ptr but found f64
Vec2 {
x: self.x * s,
y: self.y * s
@ -28,6 +43,22 @@ impl Mul<Vec2, f64> for Vec2 {
}
}
pub fn main() {
Vec2 { x: 1.0, y: 2.0 } * 2.0;
struct Vec3 {
x: f64,
y: f64,
z: f64
}
// Unexpected return type
impl Mul<f64, i32> for Vec3 {
fn mul(&self, s: &f64) -> f64 {
//~^ ERROR: method `mul` has an incompatible type for trait: expected i32 but found f64
*s
}
}
pub fn main() {
Vec1 { x: 1.0 } * 2.0;
Vec2 { x: 1.0, y: 2.0 } * 2.0;
Vec3 { x: 1.0, y: 2.0, z: 3.0 } * 2.0;
}