Updating D beyond Unicode 2.0

[Neia Neutuladh]

On Saturday, 22 September 2018 at 08:52:32 UTC, Jonathan M Davis 
wrote:
> Unicode identifiers may make sense in a code base that is going 
> to be used solely by a group of developers who speak a 
> particular language that uses a number a of non-ASCII 
> characters (especially languages like Chinese or Japanese), but 
> it has no business in any code that's intended for 
> international use. It just causes problems.

You have a problem when you need to share a codebase between two 
organizations using different languages. "Just use ASCII" is not 
the solution. "Use a language that most developers in both 
organizations can use" is. That's *usually* going to be English, 
but not always. For instance, a Belorussian company doing 
outsourcing work for a Russian company might reasonably write 
code in Russian.

If you're writing for a global audience, as most open source code 
is, you're usually going to use the most widely spoken language.