Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Modularization
See original GitHub issueHello. I’m currently working on a library for Android which requires JSON parsing. My requirements are: — small methods count (DEX limit); — small bytecode size (smaller APK and faster verification); — high parsing speed.
I totally like your parser. I’ve took your streaming code, removed <T> parsing, Any type, and some other unused stuff; inlined one-liners.
My result is <50 methods and 10.8 KB DEX 😃
I think it makes sense to move streaming to another module/artifact so those who need only streaming may use it without other parser parts.
Issue Analytics
- State:
- Created 6 years ago
- Reactions:2
- Comments:9 (7 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
@Miha-x64 https://github.com/json-iterator/java-core invited you to host the development
Sadly, Android requires 1.6 bytecode, and this parser is very helpful there since
org.json, embedded in Android, totally sucks.You can just add module-info into your JAR.