> It isn't about fear, it's because I find longer names to be suggestive of a longer life for the name. Shorter names, abbreviations names, etc., are suggestive of short life, lightweight variables. That's, for example, why ScopeBuffer is spelled out, instead of being SBuf.

I just don't agree. When I see single letter names or abbreviated names I see laziness for coming up with a descriptive name.

> just looks like wordy mc-word excess to me. Consider also that opSlice has a conventional purpose, and is used for exactly that conventional purpose. If it did something surprising, I'd be more inclined to agree that more clues to that would be desirable.

Public API names should be clear and descriptive.

> I agree that DMD source code can often be confusing, but I don't agree it is because of short names being used. The code has a particular language style, and names that follow usually predictable patterns, and those predictable patterns help in understanding. For example, the scope variable is always 'sc', and 't' is used for types, etc. I find in reading the code that the predictable patterns help enormously, much more than longer names would.

Of course you don't agree with me since you wrote the code. When I read the DMD source code I have to constantly scroll back to the definition of a variable to read the comment describing what the variable does. Comments like this is a code smell do me. Instead of having a comment, just use a clear name the describes the variable instead.