Open
Conversation
[skip ci]
Author
|
Hi, I really liked/like your work, and this lazy idea, that I believe I may have heard of it first related to your package. I'm not disrespecting your work. I just believe JSON3.jl is well tested by now, and know it came later, and your and JSON.jl are pre-1.0 (I made similar suggestion there). Is you fully supported, and better in some way? https://discourse.julialang.org/t/announce-a-different-way-to-read-json-data-lazyjson-jl/9046 @quinnj, FYI (not a huge concern, I doubt many would use both at once): In my 1-day master, JSON3 loads a tiny bit faster, and combined almost as fast if loaded in reverse order, but with this order loading your first penalizes JSON3 a lot: |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
[skip ci]