I agree it would.
After thinking more about it, making unicode escapes handle the same way as any other escape would have my personal preference.
That would lose you the possibility to use unicode escapes to represent arbitrary syntax. I don’t think anyone would lose sleep over the fact that you then no longer can write
\u0076\u0061\u006c\u0020\u0078\u0020\u003d\u0020\u0037 instead of
val x = 7.
You do use the ability to use unicode escapes for identifiers that aren’t back-quoted. That might be a bit more cumbersome in the general case, and disallows using unicode escapes in identifiers in match cases (since back-quoted escapes have a special meaning there).
I’d love to check whether there are any uses of that feature in the community build, and how often unicode escapes are used in a way that wouldn’t be supported by this scheme.