mikros/rust
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
7721c7319d
rust/tests/ui/reify-intrinsic.stderr

Ignoring revisions in .git-blame-ignore-revs. Click here to bypass and see the normal blame view.

33 lines
1.6 KiB
Plaintext
Raw Normal View History

Emit error on intrinsic to fn ptr casts
2019-09-02 16:28:37 -05:00
error[E0308]: cannot coerce intrinsics to function pointers
--> $DIR/reify-intrinsic.rs:6:64
|
LL | let _: unsafe extern "rust-intrinsic" fn(isize) -> usize = std::mem::transmute;
Increase verbosity when suggesting subtle code changes
2020-03-11 22:38:21 -05:00
| ------------------------------------------------- ^^^^^^^^^^^^^^^^^^^ cannot coerce intrinsics to function pointers
| |
Point at type in `let` assignment on type errors
2019-11-18 23:00:24 -06:00
| expected due to this
Emit error on intrinsic to fn ptr casts
2019-09-02 16:28:37 -05:00
|
Specific labels when referring to "expected" and "found" types
2019-11-13 16:16:56 -06:00
= note: expected fn pointer `unsafe extern "rust-intrinsic" fn(isize) -> usize`
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
found fn item `unsafe extern "rust-intrinsic" fn(_) -> _ {transmute::<_, _>}`
Mention fn coercion rules (needs to be expanded)
2023-01-06 14:15:10 -06:00
= note: when the arguments and return types match, functions can be coerced to function pointers
Emit error on intrinsic to fn ptr casts
2019-09-02 16:28:37 -05:00
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
error[E0606]: casting `unsafe extern "rust-intrinsic" fn(_) -> _ {transmute::<_, _>}` as `unsafe extern "rust-intrinsic" fn(isize) -> usize` is invalid
Emit error on intrinsic to fn ptr casts
2019-09-02 16:28:37 -05:00
--> $DIR/reify-intrinsic.rs:11:13
|
LL | let _ = std::mem::transmute as unsafe extern "rust-intrinsic" fn(isize) -> usize;
| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Check for intrinsics before coercing to a function pointer Return an error if coercing function items / non-capturing closures to a common function pointer type would require reifying an intrinsic.
2021-04-20 19:00:00 -05:00
error[E0308]: cannot coerce intrinsics to function pointers
--> $DIR/reify-intrinsic.rs:18:9
|
Change test to use `likely`/`unlikely` instead of `copy`/`copy_overlapping`. Test was added in PR #84404. The intent here is: The `copy`/`copy_overlapping` intrinsics are going through some flip-flopping now of "are they intrinsics or not". We can achieve the same effect that the test intended by using `likely`/`unlikely`.
2021-06-04 14:37:16 -05:00
LL | std::intrinsics::unlikely,
| ^^^^^^^^^^^^^^^^^^^^^^^^^ cannot coerce intrinsics to function pointers
Check for intrinsics before coercing to a function pointer Return an error if coercing function items / non-capturing closures to a common function pointer type would require reifying an intrinsic.
2021-04-20 19:00:00 -05:00
|
Resolve vars in note_type_err
2022-04-17 14:00:32 -05:00
= note: expected fn item `extern "rust-intrinsic" fn(_) -> _ {likely}`
found fn item `extern "rust-intrinsic" fn(_) -> _ {unlikely}`
Add suggestions for function pointers - On compiler-error's suggestion of moving this lower down the stack, along the path of `report_mismatched_types()`, which is used by `rustc_hir_analysis` and `rustc_hir_typeck`. - update ui tests, add test - add suggestions for references to fn pointers - modify `TypeErrCtxt::same_type_modulo_infer` to take `T: relate::Relate` instead of `Ty`
2022-12-11 01:49:07 -06:00
= note: different fn items have unique types, even if their signatures are the same
Check for intrinsics before coercing to a function pointer Return an error if coercing function items / non-capturing closures to a common function pointer type would require reifying an intrinsic.
2021-04-20 19:00:00 -05:00
error: aborting due to 3 previous errors
Emit error on intrinsic to fn ptr casts
2019-09-02 16:28:37 -05:00
Some errors have detailed explanations: E0308, E0606.
For more information about an error, try `rustc --explain E0308`.
Reference in New Issue Copy Permalink