Release 2.069.0 introduced line numbers in stack traces, but they are often wrong.
Consider the trivial example:
-----some.d-----
void main ()
{
assert (false);
}
-----
Compile as "dmd -g some.d" to 32-bit Windows executable.
Here is the error message up to 2.068.2 release:
[email protected](3): Assertion failure
<...>
0x00402054 in main
<...>
And here is the error message in 2.069.0 and up:
[email protected](3): Assertion failure
<...>
0x00402054 in main at <...>\some.d(7)
<...>
Here, "some.d(7)" is file and line number. Obviously, it is wrong, and the line should be 3.