On Thursday, 29 January 2015 at 18:47:37 UTC, Rory McGuire wrote:
used that is possibly easier to work with JSON values.
On Thu, Jan 29, 2015 at 5:18 PM, BlackEdder via
On Thursday, 29 January 2015 at 14:05:25 UTC, Chris wrote:
Yeah, I was wondering, if you have to import std.json and use
it as a
basis for painlessjson, is it really so big an improvement?
since std.json might be replaced (sooner or later). I'd
prefer an "easy to
use" implementation that replaces std.json completely.
Painlessjson in many ways abstracts away the std.json
using it you should rarely/never have to use std.json
basically abstracts away most of the complexity and you should
have to use toJSON and fromJSON. This works with built-in types
(double/int/string etc.) and also with ranges and associative
On top of that Painlessjson also makes it easy to convert your
types/struct/classes to and from JSON by (de)serializing them
(as far as possible).
If a better simpler std.json gets developed then we can rebase
painlessjson on that and it might become a thinner wrapper,
but I would
expect the (de)serialization still to be useful in many cases.
It's fun to see that there are so many different solutions to
working with JSON in D. jsvar seems to be for keeping your
most cases. The idea of painlessjson is to convert to native D as
fast as possible. The goal is to get something like
https://github.com/FasterXML/jackson for D.
We are still looking for input on how inheritance and
constructors should work.