> perhaps unsafe blocks ought to be renamed to safe blocks

We have had long and heated discussions on this topic, actually. My personal position is that the code inside such a block has fundamental tension: the compiler must assume that it is safe, while the programmer must in all cases admit the possibility that it is unsafe. Given that keywords should be optimized for the reader rather than the compiler, I prefer `unsafe` to `safe`.

However, that's not to say that there doesn't exist a better word entirely. Perhaps `unchecked` would suffice...