mikros/rust
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
2d45df3caa
rust/tests/ui/statics/uninhabited-static.stderr

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

86 lines
3.6 KiB
Plaintext
Raw Normal View History

ensure that statics are inhabited
2020-10-24 09:13:39 -05:00
error: static of uninhabited type
--> $DIR/uninhabited-static.rs:6:5
|
LL | static VOID: Void;
Move item_span from check_item_type into each function
2022-07-07 21:32:51 -05:00
| ^^^^^^^^^^^^^^^^^
ensure that statics are inhabited
2020-10-24 09:13:39 -05:00
|
bless ui tests
2022-09-18 10:55:36 -05:00
= warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in a future release!
= note: for more information, see issue #74840 <https://github.com/rust-lang/rust/issues/74840>
= note: uninhabited statics cannot be initialized, and any access would be an immediate error
ensure that statics are inhabited
2020-10-24 09:13:39 -05:00
note: the lint level is defined here
--> $DIR/uninhabited-static.rs:2:9
|
LL | #![deny(uninhabited_static)]
| ^^^^^^^^^^^^^^^^^^
error: static of uninhabited type
--> $DIR/uninhabited-static.rs:8:5
|
LL | static NEVER: !;
Move item_span from check_item_type into each function
2022-07-07 21:32:51 -05:00
| ^^^^^^^^^^^^^^^
ensure that statics are inhabited
2020-10-24 09:13:39 -05:00
|
= warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in a future release!
= note: for more information, see issue #74840 <https://github.com/rust-lang/rust/issues/74840>
= note: uninhabited statics cannot be initialized, and any access would be an immediate error
also test non-extern uninhabited statics
2020-10-25 09:01:32 -05:00
error: static of uninhabited type
--> $DIR/uninhabited-static.rs:12:1
|
LL | static VOID2: Void = unsafe { std::mem::transmute(()) };
Shorten def_span for more items.
2022-02-13 09:27:59 -06:00
| ^^^^^^^^^^^^^^^^^^
also test non-extern uninhabited statics
2020-10-25 09:01:32 -05:00
|
= warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in a future release!
= note: for more information, see issue #74840 <https://github.com/rust-lang/rust/issues/74840>
= note: uninhabited statics cannot be initialized, and any access would be an immediate error
error: static of uninhabited type
Don't abort compilation after giving a lint error The only reason to use `abort_if_errors` is when the program is so broken that either: 1. later passes get confused and ICE 2. any diagnostics from later passes would be noise This is never the case for lints, because the compiler has to be able to deal with `allow`-ed lints. So it can continue to lint and compile even if there are lint errors.
2021-07-20 22:23:22 -05:00
--> $DIR/uninhabited-static.rs:16:1
also test non-extern uninhabited statics
2020-10-25 09:01:32 -05:00
|
LL | static NEVER2: Void = unsafe { std::mem::transmute(()) };
Shorten def_span for more items.
2022-02-13 09:27:59 -06:00
| ^^^^^^^^^^^^^^^^^^^
also test non-extern uninhabited statics
2020-10-25 09:01:32 -05:00
|
= warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in a future release!
= note: for more information, see issue #74840 <https://github.com/rust-lang/rust/issues/74840>
= note: uninhabited statics cannot be initialized, and any access would be an immediate error
Check if call return type is visibly uninhabited when building MIR
2022-01-24 18:00:00 -06:00
error[E0080]: could not evaluate static initializer
--> $DIR/uninhabited-static.rs:12:31
Don't abort compilation after giving a lint error The only reason to use `abort_if_errors` is when the program is so broken that either: 1. later passes get confused and ICE 2. any diagnostics from later passes would be noise This is never the case for lints, because the compiler has to be able to deal with `allow`-ed lints. So it can continue to lint and compile even if there are lint errors.
2021-07-20 22:23:22 -05:00
|
LL | static VOID2: Void = unsafe { std::mem::transmute(()) };
Use translatable diagnostics in `rustc_const_eval`
2023-05-17 05:30:14 -05:00
| ^^^^^^^^^^^^^^^^^^^^^^^ constructing invalid value: encountered a value of uninhabited type `Void`
Don't abort compilation after giving a lint error The only reason to use `abort_if_errors` is when the program is so broken that either: 1. later passes get confused and ICE 2. any diagnostics from later passes would be noise This is never the case for lints, because the compiler has to be able to deal with `allow`-ed lints. So it can continue to lint and compile even if there are lint errors.
2021-07-20 22:23:22 -05:00
warning: the type `Void` does not permit zero-initialization
--> $DIR/uninhabited-static.rs:12:31
|
LL | static VOID2: Void = unsafe { std::mem::transmute(()) };
lint: don't suggest assume_init for uninhabited types
2023-02-13 08:38:23 -06:00
| ^^^^^^^^^^^^^^^^^^^^^^^ this code causes undefined behavior when executed
Don't abort compilation after giving a lint error The only reason to use `abort_if_errors` is when the program is so broken that either: 1. later passes get confused and ICE 2. any diagnostics from later passes would be noise This is never the case for lints, because the compiler has to be able to deal with `allow`-ed lints. So it can continue to lint and compile even if there are lint errors.
2021-07-20 22:23:22 -05:00
|
make invalid_value lint a bit smarter around enums
2022-09-25 15:56:01 -05:00
note: enums with no inhabited variants have no valid value
--> $DIR/uninhabited-static.rs:4:1
|
LL | enum Void {}
| ^^^^^^^^^
bless ui tests
2022-09-18 10:55:36 -05:00
= note: `#[warn(invalid_value)]` on by default
Don't abort compilation after giving a lint error The only reason to use `abort_if_errors` is when the program is so broken that either: 1. later passes get confused and ICE 2. any diagnostics from later passes would be noise This is never the case for lints, because the compiler has to be able to deal with `allow`-ed lints. So it can continue to lint and compile even if there are lint errors.
2021-07-20 22:23:22 -05:00
Make some lints incremental.
2022-06-18 12:48:44 -05:00
error[E0080]: could not evaluate static initializer
--> $DIR/uninhabited-static.rs:16:32
|
LL | static NEVER2: Void = unsafe { std::mem::transmute(()) };
Use translatable diagnostics in `rustc_const_eval`
2023-05-17 05:30:14 -05:00
| ^^^^^^^^^^^^^^^^^^^^^^^ constructing invalid value: encountered a value of uninhabited type `Void`
Make some lints incremental.
2022-06-18 12:48:44 -05:00
Don't abort compilation after giving a lint error The only reason to use `abort_if_errors` is when the program is so broken that either: 1. later passes get confused and ICE 2. any diagnostics from later passes would be noise This is never the case for lints, because the compiler has to be able to deal with `allow`-ed lints. So it can continue to lint and compile even if there are lint errors.
2021-07-20 22:23:22 -05:00
warning: the type `Void` does not permit zero-initialization
--> $DIR/uninhabited-static.rs:16:32
|
LL | static NEVER2: Void = unsafe { std::mem::transmute(()) };
lint: don't suggest assume_init for uninhabited types
2023-02-13 08:38:23 -06:00
| ^^^^^^^^^^^^^^^^^^^^^^^ this code causes undefined behavior when executed
Don't abort compilation after giving a lint error The only reason to use `abort_if_errors` is when the program is so broken that either: 1. later passes get confused and ICE 2. any diagnostics from later passes would be noise This is never the case for lints, because the compiler has to be able to deal with `allow`-ed lints. So it can continue to lint and compile even if there are lint errors.
2021-07-20 22:23:22 -05:00
|
make invalid_value lint a bit smarter around enums
2022-09-25 15:56:01 -05:00
note: enums with no inhabited variants have no valid value
--> $DIR/uninhabited-static.rs:4:1
|
LL | enum Void {}
| ^^^^^^^^^
Don't abort compilation after giving a lint error The only reason to use `abort_if_errors` is when the program is so broken that either: 1. later passes get confused and ICE 2. any diagnostics from later passes would be noise This is never the case for lints, because the compiler has to be able to deal with `allow`-ed lints. So it can continue to lint and compile even if there are lint errors.
2021-07-20 22:23:22 -05:00
error: aborting due to 6 previous errors; 2 warnings emitted
ensure that statics are inhabited
2020-10-24 09:13:39 -05:00
Don't abort compilation after giving a lint error The only reason to use `abort_if_errors` is when the program is so broken that either: 1. later passes get confused and ICE 2. any diagnostics from later passes would be noise This is never the case for lints, because the compiler has to be able to deal with `allow`-ed lints. So it can continue to lint and compile even if there are lint errors.
2021-07-20 22:23:22 -05:00
For more information about this error, try `rustc --explain E0080`.
Reference in New Issue Copy Permalink