Would be nice if compiler gave more information!

[Vladimir Panteleev]

On Friday, 15 June 2018 at 03:54:34 UTC, DigitalDesigns wrote:
> So, it should be very important to have some type of info that 
> connects the error to what the compiler was doing. With large 
> problems it is not easy to reduce to a test case that shows the 
> problem directly.

In my experience as a layman as far as DMD internals go, a 
compiler stack trace generally does little to elucidate what the 
cause of the crash is, or especially what part of the program is 
responsible. Tools to reduce the input (DustMite, or Digger for 
regressions) are generally more effective.

> I think a debug build dmd would be the easiest way. It is built 
> with the release version so they are identical... but it would 
> help users to quickly help with compiler errors rather than 
> having to go build the compiler themselves, etc.

FWIW, Digger can build debug DMD binaries with `-c 
build.components.dmd.debugDMD=true`.