Thank you, I had the same fuzzy thought in the back of my mind while reading this but couldn’t quite put it into words. The idea of depending on developers to u

Thank you, I had the same fuzzy thought in the back of my mind while reading this but couldn’t quite put it into words. The idea of depending on developers to understand “usFoo” means this is an unsafe string and “sFoo” means this is a safe string seems error prone. Those rely on the developer knowing what “us” and “s” represent. A much better idea would be to give that information to the compiler, so the developer can get a useful error if they try to do something unsafe. We should try to turn these onto compiler errors as much as possible so if a developer does something bad, it wont even compile. This seems like a much more fool proof way to accomplish what the author is trying to do.