On Monday, 19 October 2020 at 14:07:38 UTC, matheus wrote:
On Sunday, 18 October 2020 at 19:24:28 UTC, Ferhat Kurtulmuş
wrote:
I plan to start a project in reasonable size, I wonder if I
should really use betterC... if I encounter a bug like this,
will I be stuck at it?
The bug report says, i
On Monday, 19 October 2020 at 14:07:38 UTC, matheus wrote:
On Sunday, 18 October 2020 at 19:24:28 UTC, Ferhat Kurtulmuş
wrote:
I plan to start a project in reasonable size, I wonder if I
should really use betterC... if I encounter a bug like this,
will I be stuck at it?
The bug report says, i
On Sunday, 18 October 2020 at 19:24:28 UTC, Ferhat Kurtulmuş
wrote:
I plan to start a project in reasonable size, I wonder if I
should really use betterC... if I encounter a bug like this,
will I be stuck at it?
The bug report says, it is a dmd specific problem, and LDC, my
favorite d compile
On Sunday, 18 October 2020 at 17:05:01 UTC, Neto wrote:
On Sunday, 18 October 2020 at 16:12:59 UTC, Paul Backus wrote:
On Sunday, 18 October 2020 at 16:04:55 UTC, Koro wrote:
I'm writing a 'betterC' program and the compiler is
generating a call to '_memset64' if I have an array literal
where t
On Sunday, 18 October 2020 at 16:12:59 UTC, Paul Backus wrote:
On Sunday, 18 October 2020 at 16:04:55 UTC, Koro wrote:
I'm writing a 'betterC' program and the compiler is generating
a call to '_memset64' if I have an array literal where the
elements are the same.
It's a known bug:
https://is
On Sunday, 18 October 2020 at 16:04:55 UTC, Koro wrote:
I'm writing a 'betterC' program and the compiler is generating
a call to '_memset64' if I have an array literal where the
elements are the same.
It's a known bug:
https://issues.dlang.org/show_bug.cgi?id=17778
My guess is that the reaso
