Dylan DPC 4dea3a295f Rollup merge of #108000 - y21:no-zero-init-for-uninhabited, r=jackh726 ... lint: don't suggest MaybeUninit::assume_init for uninhabited types Creating a zeroed uninhabited type such as `!` or an empty enum with `mem::zeroed()` (or transmuting `()` to `!`) currently triggers this lint: ```rs warning: the type `!` does not permit zero-initialization --> test.rs:5:23 | 5 | let _val: ! = mem::zeroed(); | ^^^^^^^^^^^^^ | | | this code causes undefined behavior when executed | help: use `MaybeUninit<T>` instead, and only call `assume_init` after initialization is done | = note: the `!` type has no valid value ``` The `MaybeUninit` suggestion in the help message seems confusing/useless for uninhabited types, as such a type cannot be fully initialized in the first place (as the note implies). This PR limits this help message to inhabited types which can be initialized		2023-02-21 14:19:58 +05:30
..
src	Rollup merge of #108000 - y21:no-zero-init-for-uninhabited, r=jackh726	2023-02-21 14:19:58 +05:30
Cargo.toml	Update unicode-rs crates to Unicode 15	2022-09-17 01:55:56 +08:00