rust/tests/ui/lub-glb/old-lub-glb-object.stderr

error[E0308]: mismatched types
  --> $DIR/old-lub-glb-object.rs:9:14
   |
LL |         _ => y,
   |              ^ one type is more general than the other
   |
   = note: expected trait object `dyn for<'a, 'b> Foo<&'a u8, &'b u8>`
              found trait object `dyn for<'a> Foo<&'a u8, &'a u8>`

error[E0308]: mismatched types
  --> $DIR/old-lub-glb-object.rs:9:14
   |
LL |         _ => y,
   |              ^ one type is more general than the other
   |
   = note: expected trait object `dyn for<'a, 'b> Foo<&'a u8, &'b u8>`
              found trait object `dyn for<'a> Foo<&'a u8, &'a u8>`

error: aborting due to 2 previous errors

For more information about this error, try `rustc --explain E0308`.
Report nicer errors for HRTB NLL errors from queries 2021-06-07 14:25:19 -05:00			`error[E0308]: mismatched types`
Fully stabilize NLL 2022-04-01 12:13:25 -05:00			`--> $DIR/old-lub-glb-object.rs:9:14`
fix subtle bug in NLL type checker The bug was revealed by the behavior of the old-lub-glb-hr-noteq1.rs test. The old-lub-glb-hr-noteq2 test shows the current 'order dependent' behavior of coercions around higher-ranked functions, at least when running with `-Zborrowck=mir`. Also, run compare-mode=nll. 2020-06-08 18:12:01 -05:00			`\|`
			`LL \| _ => y,`
Report nicer errors for HRTB NLL errors from queries 2021-06-07 14:25:19 -05:00			`\| ^ one type is more general than the other`
			`\|`
Don't anonymize bound region names during typeck Once this anonymization has performed, we have no way of recovering the original names during NLL borrow checking. Keeping the original names allows error messages in full NLL mode to contain the original bound region names. As a result, the typeck results may contain types that differ only in the names used for their bound regions. However, anonimization of bound regions does not guarantee that all distinct types are unqual (e.g. not subtypes of each other). For example, `for<'a> fn(&'a u32, &'a u32)` and `for<'b, 'c> fn(&'b u32, &'c u32)` are subtypes of each other, as explained here: https://github.com/rust-lang/rust/blob/63cc2bb3d07d6c726dfcdc5f95cbe5ed4760641a/compiler/rustc_infer/src/infer/nll_relate/mod.rs#L682-L690 Therefore, any code handling types with higher-ranked regions already needs to handle the case where two distinct `Ty`s are 'actually' equal. 2021-09-25 13:04:00 -05:00			= note: expected trait object `dyn for<'a, 'b> Foo<&'a u8, &'b u8>`
			found trait object `dyn for<'a> Foo<&'a u8, &'a u8>`
fix subtle bug in NLL type checker The bug was revealed by the behavior of the old-lub-glb-hr-noteq1.rs test. The old-lub-glb-hr-noteq2 test shows the current 'order dependent' behavior of coercions around higher-ranked functions, at least when running with `-Zborrowck=mir`. Also, run compare-mode=nll. 2020-06-08 18:12:01 -05:00
Report nicer errors for HRTB NLL errors from queries 2021-06-07 14:25:19 -05:00			`error[E0308]: mismatched types`
Fully stabilize NLL 2022-04-01 12:13:25 -05:00			`--> $DIR/old-lub-glb-object.rs:9:14`
fix subtle bug in NLL type checker The bug was revealed by the behavior of the old-lub-glb-hr-noteq1.rs test. The old-lub-glb-hr-noteq2 test shows the current 'order dependent' behavior of coercions around higher-ranked functions, at least when running with `-Zborrowck=mir`. Also, run compare-mode=nll. 2020-06-08 18:12:01 -05:00			`\|`
			`LL \| _ => y,`
Report nicer errors for HRTB NLL errors from queries 2021-06-07 14:25:19 -05:00			`\| ^ one type is more general than the other`
			`\|`
Don't anonymize bound region names during typeck Once this anonymization has performed, we have no way of recovering the original names during NLL borrow checking. Keeping the original names allows error messages in full NLL mode to contain the original bound region names. As a result, the typeck results may contain types that differ only in the names used for their bound regions. However, anonimization of bound regions does not guarantee that all distinct types are unqual (e.g. not subtypes of each other). For example, `for<'a> fn(&'a u32, &'a u32)` and `for<'b, 'c> fn(&'b u32, &'c u32)` are subtypes of each other, as explained here: https://github.com/rust-lang/rust/blob/63cc2bb3d07d6c726dfcdc5f95cbe5ed4760641a/compiler/rustc_infer/src/infer/nll_relate/mod.rs#L682-L690 Therefore, any code handling types with higher-ranked regions already needs to handle the case where two distinct `Ty`s are 'actually' equal. 2021-09-25 13:04:00 -05:00			= note: expected trait object `dyn for<'a, 'b> Foo<&'a u8, &'b u8>`
			found trait object `dyn for<'a> Foo<&'a u8, &'a u8>`
fix subtle bug in NLL type checker The bug was revealed by the behavior of the old-lub-glb-hr-noteq1.rs test. The old-lub-glb-hr-noteq2 test shows the current 'order dependent' behavior of coercions around higher-ranked functions, at least when running with `-Zborrowck=mir`. Also, run compare-mode=nll. 2020-06-08 18:12:01 -05:00
			`error: aborting due to 2 previous errors`

Report nicer errors for HRTB NLL errors from queries 2021-06-07 14:25:19 -05:00			For more information about this error, try `rustc --explain E0308`.