"Jens Bauer" wrote in message news:[email protected]...
I expect to get more information about this, and of course, I hope to find
what causes the bug.
When my next build is finished, I plan to add a zero in front of the
number 3:
uint[03] message =
... just in case it's a read-pointer "alignment-style" problem.
You can tell how far through the error is by triggering failures in
different compilation phases.
eg to generate a parser error, give the compiler something invalid like:
pragma 3
which should generate
testx.d(2): Error: found '3' when expecting '('
This should error during semantic2
static assert(3 == 2);
