Eugene-Dash comments

Results 5 comments of


                                            Eugene-Dash

Updated Example API Usage in README to work with the newest version (0.4.1)

I had to do the same thing to get it working

Add `std.json.ParseOptions.parse_numbers` to preserve float precision

The exact schema of the JSON in my use case could not be assumed, writing a custom json.Value like enum is the solution that I used to handle those variations...

Add `std.json.ParseOptions.parse_numbers` to preserve float precision

My reasoning for adding the option to integers, was that some floating point values would find themselves parsed as integers if they fell on whole numbers; the ```parse_integers``` option is...

Add `std.json.ParseOptions.parse_numbers` to preserve float precision

I can't answer that. In fact, if it was one unified option, I can think of three advantages. 1. The parsing speed would be faster while not parsing numbers, due...

Add `std.json.ParseOptions.parse_numbers` to preserve float precision

Used the ```zig fmt``` command to format ```dynamic.zig``` and ```dynamic_tests.zig```. The files' formatting was invalid due to an unnecessary newline character and an instance of invalid indentation; hence the failed...