Walter's DConf 2014 Talks - Topics in Finance

[Walter Bright]

On 3/23/2014 10:38 AM, Sean Kelly wrote:
> Try no funding and a trivial amount of time.  The JSON parser I wrote for work
> in C performs zero allocations and unescaping is performed on demand.  D
> arguably makes this easier by building slicing into the language, but not
> decoding or copying is a design decision, not a language artifact (at least in
> the case of C/C++ where aliasing data is allowed).  The take-away from that
> Tango article is that the performance hit for parsing is aggressively decoding
> data the user may not care about or may not want decoded in the first place.
> This just happens to be the approach that basically every XML parser on the
> planet uses for some ridiculous reason.

Lazy evaluation FTW. Ranges and algorithms fit right in with that.