Would it make sense to implement String as a sealed class with Latin1 and UTF-16 subclasses?
Ignoring backward-compatibility constraints, would there be any real advantage to changing Java's String implementation from one final class with an internal `byte coder` field into a sealed hierarchy…