On Thursday, 3 April 2014 at 06:23:40 UTC, Jonathan M Davis wrote:
On Tuesday, April 01, 2014 03:54:07 Jonathan M Davis wrote:
On Tuesday, April 01, 2014 05:35:28 ed wrote:
> OK, lazy me just read the std.satetime article again. It
> appears
> the design is for no invalid values and it is curre
On Tuesday, April 01, 2014 03:54:07 Jonathan M Davis wrote:
> On Tuesday, April 01, 2014 05:35:28 ed wrote:
> > OK, lazy me just read the std.satetime article again. It appears
> > the design is for no invalid values and it is currently a known
> > limitation due to CTFE.
> >
> > ---
> > d_time_na
On Tuesday, 1 April 2014 at 10:54:41 UTC, Jonathan M Davis wrote:
On Tuesday, April 01, 2014 05:35:28 ed wrote:
OK, lazy me just read the std.satetime article again. It
appears
the design is for no invalid values and it is currently a known
limitation due to CTFE.
---
d_time_nan There is no eq
On Tuesday, April 01, 2014 05:35:28 ed wrote:
> OK, lazy me just read the std.satetime article again. It appears
> the design is for no invalid values and it is currently a known
> limitation due to CTFE.
>
> ---
> d_time_nanThere is no equivalent. SysTime.init, which has a null
> TimeZone obj
OK, lazy me just read the std.satetime article again. It appears
the design is for no invalid values and it is currently a known
limitation due to CTFE.
---
d_time_nan There is no equivalent. SysTime.init, which has a null
TimeZone object, would be the closest, but once CTFE advances to
the
Hi All,
I'm trying to use SysTime in a struct but I've noticed the
following:
(A) SysTime.init leads to a crash.
---
void main()
{
SysTime t;
writefln("t:%s", t);
}
% ./dtest
zsh: segmentation fault (core dumped) ./dtest
---
(B) Initialising a SysTime member directly fails
---
struc
