Mem::uninitialized, `!` and trap representations

nikomatsakis · January 12, 2017, 6:45pm

I mentioned this discussion in this thread, which discusses the impact of a recent change in exhaustiveness checking – it seems somewhat at odds with what we were discussing here.

Topic		Replies	Views
Make mem::uninitialized and mem::zeroed panic for (some) types where 0 is a niche Unsafe Code Guidelines	29	3893	August 16, 2019
Memcpy and uninitialized memory Unsafe Code Guidelines	19	3194	August 17, 2020
Role of UB / uninitialized memory Unsafe Code Guidelines	78	9507	March 25, 2019
Safely reading uninitialized memory	25	3003	March 25, 2019
`mem::uninitialized` and `const fn` libs	5	1520	March 25, 2019

Mem::uninitialized, `!` and trap representations

Related topics