I just hit a problem in my serialization library, Orange, being
integrated as std.serialization. The format of .stringof changed in git
HEAD. Now, the question is should the format of .stringof be defined and
reliable or not defined at all? Either way, this should be clearly
stated
On Friday, 13 September 2013 at 07:06:27 UTC, Jacob Carlborg
wrote:
I just hit a problem in my serialization library, Orange, being
integrated as std.serialization. The format of .stringof
changed in git HEAD. Now, the question is should the format of
.stringof be defined and reliable
On 2013-09-13 09:11, Brian Schott wrote:
Funny. I just ran into that with msgpack-d in my project... So
that's two libraries broken.
I guess __traits(identifier, Foo.tupleof[0]) is more reliable than
.strinfof. But it would be nice to once and for all get an official
agreement on this
On Friday, 13 September 2013 at 07:06:27 UTC, Jacob Carlborg
wrote:
I just hit a problem in my serialization library, Orange, being
integrated as std.serialization. The format of .stringof
changed in git HEAD. Now, the question is should the format of
.stringof be defined and reliable
