Disable Javy.JSON by default #671
Merged
Conversation
This file contains 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
Prior to this commit this option was true by default in order to profit of the performance benefits of SIMD JSON. Unfortunately this introduced issues with GC which need to be investigated further. In the meantime we're setting as off by default.
saulecabrera
force-pushed
the
disable-javy-json-temporarily
branch
from
7f06fde to
e87db51
Compare
jeffcharles
approved these changes
Jun 18, 2024
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.
Description of the change
Prior to this commit this option was true by default in order to profit of the performance benefits of SIMD JSON. Unfortunately this introduced issues with GC which need to be investigated further. In the meantime we're setting as off by default.
Checklist
javy-cliandjavy-coredo not require updating CHANGELOG files.