https://issues.dlang.org/show_bug.cgi?id=17740
Iain Buclaw changed:
What|Removed |Added
Priority|P1 |P3
--
https://issues.dlang.org/show_bug.cgi?id=17740
--- Comment #9 from Mr. Smith ---
Error doesn't happen when `import std.datetime : MonoTime;` is removed
--
https://issues.dlang.org/show_bug.cgi?id=17740
--- Comment #8 from Steven Schveighoffer ---
Correction: PR was not about MonoTime but SysTime. But still, datetime seems to
be involved.
--
https://issues.dlang.org/show_bug.cgi?id=17740
--- Comment #7 from Steven Schveighoffer ---
Hm... I didn't see this before, but you have an import for MonoTime. On the
original PR I saw this, it was an update to MonoTime.
Can you confirm that your code works or not without MonoTime import (which
https://issues.dlang.org/show_bug.cgi?id=17740
--- Comment #6 from Mr. Smith ---
Looks like the problem is with
Piece* sentinel = new Piece;
If I do that at runtime it works.
--
https://issues.dlang.org/show_bug.cgi?id=17740
Mr. Smith changed:
What|Removed |Added
CC||mrsmit...@yandex.ru
--- Comment #5 from Mr. Smit
https://issues.dlang.org/show_bug.cgi?id=17740
--- Comment #4 from Steven Schveighoffer ---
A better reduced test case:
https://gist.github.com/MrSmith33/dc53d8cb6ce642fcb6dbc5863d029cec
Courtesy of MrSmith:
https://forum.dlang.org/post/ahoyjzxreidgosqij...@forum.dlang.org
--
https://issues.dlang.org/show_bug.cgi?id=17740
Jonathan M Davis changed:
What|Removed |Added
CC||issues.dl...@jmdavisprog.co
https://issues.dlang.org/show_bug.cgi?id=17740
--- Comment #2 from Jonathan M Davis ---
Well, it looks like it relates to directly assigning a non-null value to the
_timezone member at compile time. The new TimeZone class declaration is not
required. All you have to do to trigger it is to change
https://issues.dlang.org/show_bug.cgi?id=17740
--- Comment #1 from Steven Schveighoffer ---
(In reply to Steven Schveighoffer from comment #0)
> Another example:
Wrong link, here it is:
https://forum.dlang.org/post/exinpcxvpdsbazyaw...@forum.dlang.org
--
10 matches
Mail list logo
