rust/tests/ui/block-result/issue-22645.rs

use std::ops::Add;

trait Scalar {}
impl Scalar for f64 {}

struct Bob;

impl<RHS: Scalar> Add <RHS> for Bob {
  type Output = Bob;
  fn add(self, rhs : RHS) -> Bob { Bob }
}

fn main() {
  let b = Bob + 3.5;
  b + 3 //~ ERROR E0277
  //~^ ERROR: mismatched types
}
Create a FreshFloatTy separate from FreshIntTy There is no subtyping relationship between the types (or their non-freshened variants), so they can not be merged. Fixes #22645 Fixes #24352 Fixes #23825 Should fix #25235 (no test in issue). Should fix #19976 (test is outdated). 2015-05-12 21:44:05 +03:00			`use std::ops::Add;`

			`trait Scalar {}`
			`impl Scalar for f64 {}`

			`struct Bob;`

			`impl<RHS: Scalar> Add <RHS> for Bob {`
			`type Output = Bob;`
rustc_typeck: correctly track "always-diverges" and "has-type-errors". 2016-10-26 02:28:20 +03:00			`fn add(self, rhs : RHS) -> Bob { Bob }`
Create a FreshFloatTy separate from FreshIntTy There is no subtyping relationship between the types (or their non-freshened variants), so they can not be merged. Fixes #22645 Fixes #24352 Fixes #23825 Should fix #25235 (no test in issue). Should fix #19976 (test is outdated). 2015-05-12 21:44:05 +03:00			`}`

			`fn main() {`
			`let b = Bob + 3.5;`
suggest adding a where-clause when that can help suggest adding a where-clause when there is an unmet trait-bound that can be satisfied if some type can implement it. 2016-03-29 20:12:31 +03:00			`b + 3 //~ ERROR E0277`
deduplicate trait errors before they are displayed Because of type inference, duplicate obligations exist and cause duplicate errors. To avoid this, only display the first error for each (predicate,span). The inclusion of the span is somewhat bikesheddy, but is the more conservative option (it does not remove some instability, as duplicate obligations are ignored by `duplicate_set` under some inference conditions). Fixes #28098 cc #21528 (is it a dupe?) 2015-09-24 19:58:00 +03:00			`//~^ ERROR: mismatched types`
Create a FreshFloatTy separate from FreshIntTy There is no subtyping relationship between the types (or their non-freshened variants), so they can not be merged. Fixes #22645 Fixes #24352 Fixes #23825 Should fix #25235 (no test in issue). Should fix #19976 (test is outdated). 2015-05-12 21:44:05 +03:00			`}`