Thanks for the quick answer!
On Friday, 12 January 2018 at 02:16:39 UTC, Adam D. Ruppe wrote:
On Friday, 12 January 2018 at 00:54:03 UTC, kdevel wrote:
$ dmd crash.d
$ ./crash
Nicholas Wilson is right that you can use = "" to work around
it, but with strings, null is supposed to behave the same way.
And this gives different (each wrong) behavior on -m32 vs -m64,
which leads me to believe you actually found a compiler bug.
dmd -O crash even produces a binary which segfaults on my machine.
Calling u.toString directly also leads to random spam, which
means it isn't even the library.
I'd file this as a compiler codegen bug.
https://issues.dlang.org/show_bug.cgi?id=18232
