Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Faster jackson defaults #289

Merged
merged 5 commits into from
Oct 8, 2024
Merged

Conversation

re-thc
Copy link
Contributor

@re-thc re-thc commented Oct 4, 2024

Faster Jackson default settings
By default Jackson does not enable faster features to ensure 100% backwards compatibility. They should be safe and are already in use by many projects.

Note that USE_FAST_DOUBLE_WRITER has been ported to Java 20 and so has been left out. Maybe something for the avaje native json to consider if not already (use built-in instead of custom)?

By default Jackson does not enable faster features to ensure 100% backwards compatibility. They should be safe and are already in use by many projects.

Note that `USE_FAST_DOUBLE_WRITER` has been ported to Java 20 and so has been left out. Maybe something for the avaje native json to consider if not already (use built-in instead of custom)?
By default Jackson does not enable faster features to ensure 100% backwards compatibility. They should be safe and are already in use by many projects.

Note that `USE_FAST_DOUBLE_WRITER` has been ported to Java 20 and so has been left out. Maybe something for the avaje native json to consider if not already (use built-in instead of custom)?
@rbygrave rbygrave added this to the 2.3 milestone Oct 8, 2024
@rbygrave rbygrave merged commit 63b4e68 into avaje:main Oct 8, 2024
5 checks passed
@rbygrave
Copy link
Contributor

rbygrave commented Oct 8, 2024

Thanks.

Note that USE_FAST_DOUBLE_WRITER has been ported to Java 20

Nice, I didn't know about that.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants