Right, I was imagining a new "safeness deprecation" capability for the compiler. As in, everywhere you use the (now) unsafe function as a safe one, you'd get a deprecation warning instead of an error.
I don't know if that'd actually be worth the effort (or even feasible), but there's been a couple of times now where something has had to go from safe to unsafe.