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 or not defined at all? Either
way, this should be clearly stated in the documentation, which
it's currently not.
Below is what's changed. It's managed to stay unchanged for the
last 6-7 years.
Before the change:
struct Foo
{
int a;
}
static assert(Foo.tupleof[0].stringof == "(Foo).a");
After the change:
static assert(Foo.tupleof[0].stringof == "a");
Funny. I just ran into that with msgpack-d in my project... So
that's two libraries broken.
