rust/tests/ui/unsafe/unsafe-subtyping.stderr

error[E0308]: mismatched types
  --> $DIR/unsafe-subtyping.rs:4:5
   |
LL | fn foo(x: Option<fn(i32)>) -> Option<unsafe fn(i32)> {
   |                               ---------------------- expected `Option<unsafe fn(i32)>` because of return type
LL |     x
   |     ^ expected unsafe fn, found normal fn
   |
   = note: expected enum `Option<unsafe fn(_)>`
              found enum `Option<fn(_)>`

error: aborting due to 1 previous error

For more information about this error, try `rustc --explain E0308`.
Moved compile-fail tests to ui tests. 2018-08-08 12:28:26 +00:00			`error[E0308]: mismatched types`
Remove licenses 2018-12-25 15:56:47 +00:00			`--> $DIR/unsafe-subtyping.rs:4:5`
Moved compile-fail tests to ui tests. 2018-08-08 12:28:26 +00:00			`\|`
			`LL \| fn foo(x: Option<fn(i32)>) -> Option<unsafe fn(i32)> {`
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 07:40:56 +00:00			\| ---------------------- expected `Option<unsafe fn(i32)>` because of return type
Update tests 2019-03-09 12:03:44 +00:00			`LL \| x`
Moved compile-fail tests to ui tests. 2018-08-08 12:28:26 +00:00			`\| ^ expected unsafe fn, found normal fn`
			`\|`
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 07:40:56 +00:00			= note: expected enum `Option<unsafe fn(_)>`
			found enum `Option<fn(_)>`
Moved compile-fail tests to ui tests. 2018-08-08 12:28:26 +00:00
Show number in error message even for one error Co-authored-by: Adrian <adrian.iosdev@gmail.com> 2023-11-21 15:44:16 +00:00			`error: aborting due to 1 previous error`
Moved compile-fail tests to ui tests. 2018-08-08 12:28:26 +00:00
			For more information about this error, try `rustc --explain E0308`.