Mem::uninitialized, `!` and trap representations

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.