mikros/rust
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
e2bba0708a
rust/src/test/ui/issues/issue-24352.stderr

26 lines
812 B
Plaintext
Raw Normal View History

Move some `compile-fail` tests to `ui`
2018-07-15 16:11:54 -05:00
error[E0277]: cannot subtract `{integer}` from `f64`
Remove licenses
2018-12-25 09:56:47 -06:00
--> $DIR/issue-24352.rs:3:12
Move some `compile-fail` tests to `ui`
2018-07-15 16:11:54 -05:00
|
Update tests
2019-03-09 06:03:44 -06:00
LL | 1.0f64 - 1
Move some `compile-fail` tests to `ui`
2018-07-15 16:11:54 -05:00
| ^ no implementation for `f64 - {integer}`
|
pretty: trim paths of unique symbols If a symbol name can only be imported from one place for a type, and as long as it was not glob-imported anywhere in the current crate, we can trim its printed path and print only the name. This has wide implications on error messages with types, for example, shortening `std::vec::Vec` to just `Vec`, as long as there is no other `Vec` importable anywhere. This adds a new '-Z trim-diagnostic-paths=false' option to control this feature. On the good path, with no diagnosis printed, we should try to avoid issuing this query, so we need to prevent trimmed_def_paths query on several cases. This change also relies on a previous commit that differentiates between `Debug` and `Display` on various rustc types, where the latter is trimmed and presented to the user and the former is not.
2020-09-02 02:40:56 -05:00
= help: the trait `Sub<{integer}>` is not implemented for `f64`
Mention implementers of unsatisfied trait When encountering an unsatisfied trait bound, if there are no other suggestions, mention all the types that *do* implement that trait: ``` error[E0277]: the trait bound `f32: Foo` is not satisfied --> $DIR/impl_wf.rs:22:6 | LL | impl Baz<f32> for f32 { } | ^^^^^^^^ the trait `Foo` is not implemented for `f32` | = help: the following other types implement trait `Foo`: Option<T> i32 str note: required by a bound in `Baz` --> $DIR/impl_wf.rs:18:31 | LL | trait Baz<U: ?Sized> where U: Foo { } | ^^^ required by this bound in `Baz` ``` Mention implementers of traits in `ImplObligation`s. Do not mention other `impl`s for closures, ranges and `?`.
2021-12-13 14:56:40 -06:00
= help: the following implementations were found:
<&'a f64 as Sub<f64>>
<&f64 as Sub<&f64>>
<f64 as Sub<&f64>>
<f64 as Sub>
Fix list length
2022-03-26 18:14:47 -05:00
<&'a f32 as Sub<f32>>
<&'a i128 as Sub<i128>>
<&'a i16 as Sub<i16>>
<&'a i32 as Sub<i32>>
Mention implementers of unsatisfied trait When encountering an unsatisfied trait bound, if there are no other suggestions, mention all the types that *do* implement that trait: ``` error[E0277]: the trait bound `f32: Foo` is not satisfied --> $DIR/impl_wf.rs:22:6 | LL | impl Baz<f32> for f32 { } | ^^^^^^^^ the trait `Foo` is not implemented for `f32` | = help: the following other types implement trait `Foo`: Option<T> i32 str note: required by a bound in `Baz` --> $DIR/impl_wf.rs:18:31 | LL | trait Baz<U: ?Sized> where U: Foo { } | ^^^ required by this bound in `Baz` ``` Mention implementers of traits in `ImplObligation`s. Do not mention other `impl`s for closures, ranges and `?`.
2021-12-13 14:56:40 -06:00
and 48 others
suggest a float literal when dividing a floating-point type by {integer} fix a message implement a rustfix-applicable suggestion implement `suggest_floating_point_literal` add `ObligationCauseCode::BinOp` remove duplicate code fix function names in uitests use `Diagnostic` instead of `DiagnosticBuilder`
2022-02-17 04:33:32 -06:00
help: consider using a floating-point literal by writing it with `.0`
|
LL | 1.0f64 - 1.0
| ++
Move some `compile-fail` tests to `ui`
2018-07-15 16:11:54 -05:00
error: aborting due to previous error
For more information about this error, try `rustc --explain E0277`.
Reference in New Issue Copy Permalink