Speed Improvements and _Json_GeneratePretty #1
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.
I copied and renamed _Json_Generate to _Json_GeneratePretty, because it produces pretty Json at default.
The copy, _Json_Generate, i then modified to no longer produce any Pretty json. So all the
, $s_ObjIndent = @TAB, $s_ObjDelEl = @CRLF, $s_ObjDelKey = "", $s_ObjDelVal = " ", $s_ArrIndent = @TAB, $s_ArrDelEl = @CRLF
got removed.I personally only need pretty json in certain circumstances. And not producing pretty json increases the Performance by alot. The required generation time is nearly halfed by this.
In a 6kb test Json, the one below. This improves the time by 200 ms (1000 Iterations).
This improvement could also be made to _JSON_addChangeDelete, but i didnt.
I also didnt touch the Dictionary.au3
random.zip