Bad argument on splitted float about jsx HOT 6 CLOSED

Hm, jsx works well with explicit_end option.

from jsx.

I'm happy you found the solution, but this behaviour is inconsistent with what I want jsx to do. I'm going to make it more intuitive. Thanks for finding it

from jsx.

the decoder is now much smarter about what's unambiguously incomplete and what is not. you should no longer need the explicit_end flag for cases that aren't ambiguous

Eshell V5.9.1 (abort with ^G)
1> {incomplete, F} = jsx:decode(<<"{"library": "jsx", "awesome":0">>).
{incomplete,#Fun}
2> F(<<".21}">>).
[{<<"library">>,<<"jsx">>},{<<"awesome">>,0.21}]

from jsx.

It works for integer() too, thanks a lot.
Is develop brach is stable enough for production use or should I wait for merge this patch into master?

from jsx.

this is the only significant difference between develop and master so it should be safe to use but there could be lurking edge cases i haven't considered. if you don't use explicit_end ever it's definitely safe

from jsx.

Ok, I'll try, thanks.

from jsx.