Scott P. Jones

Can you tag a version that works with v0.4.x, so that v0.4 can continue to be supported? (It looks like there are some changes coming to v0.5 that IMO will...

For one thing, `peek` isn't even exported, and it is not implemented for `TCPStream` in v0.6.2. I haven't tried yet on master. (The peek implementation looked like it might hurt...

I'm not sure why it was left unexported in master, but at least there it is better supported (instead of just 2 methods, it has 7, including `peek(s::Base.LibuvStream) in Base...

One character (really, 1 byte) look-ahead is all that the JSON format needs, and that is only for numbers (everything else is terminated by a byte that is known in...

As far as the fallback on slow parsing, I think instead, the approach of calculating the correct length first (which can be very fast, simply scan for `\`, sum up...

I wasn't aware of the test suite, that's great. I found some bugs (which I've fixed in my parsing rewrite PR that I'm reading in), I'm sure that test suite...

I thought he represented NaN and Inf somehow using just the first format. I've _got_ to finish reading his book to at least attempt to comment intelligently on this! :person_frowning:

Ah, that would be fine, for me, best if they are all in one place, so I just don't store them when I pack numbers, and can recreate them upon...

I was thinking also about your decimal unum idea, and how they could be represented in printed form, without losing information. maybe something like: ``` julia unum"~-1.23400e-20" ``` with the...

I think EBASE should just be a bit, binary or 10, no others are really worthwhile for this.