The problem with a `&'static` pointer is that it's very easy to accidentally and automatically coerce it to any lifetime. If it were a `*mut` pointer then it would be difficult to accidentally shoot yourself in the foot (although still possible), so I think that just because it's got `Raw` in the name doesn't really convey how unsafe it really is.

Plus as a bonus I think that this would fix the `%?` repr (which might actually be pretty convenient)