Some Observations on the D Development Process

[Walter Bright]

On 1/4/2018 7:41 PM, Mike Franklin wrote:
> If you have simple, mundane work that needs to be done, make a list and send it 
> my way; you should have my e-mail address.  But please be specific; "fix error 
> messages" is just going to get a reply from me asking questions.

Ok, fix error messages, like you've seen me doing already. To find which files 
need work,

     grep "error(" *.d

does the trick, turning up:

ctfeexpr.d
dimport.d
dinterpret.d
dscope.d
e2ir.d
expression.d
expressionsem.d
func.d
glue.d
iasm.d
mtype.d
nogc.d
nspace.d
opover.d
optimize.d
s2ir.d

as needing ` `. There's a lot of work just there :-( It's best to resist the 
urge to do more than just add in ` ` where they are obviously appropriate. Don't 
make perfection the enemy of better. I've found it best to have only one PR for 
this at a time, otherwise it's a lot of extra work rebasing.

A longer term goal is to find ways to refactor the code to make maximum use of 
pure, const, scope, and nothrow.

I appreciate any and all help with this.