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

Optimize KotlinNamesAnnotationIntrospector.findImplicitPropertyName method. #456

Closed

Conversation

k163377
Copy link
Contributor

@k163377 k163377 commented May 30, 2021

This PR is an excerpt of the optimization part of findImplicitPropertyNam from #451.
The following explanation is taken from #451 (comment) .


The isInlineClass checks if there is a method with a name containing - in the class that defines the Method.
On the other hand, the findImplicitPropertyName checks if the name of the getter contains -.
This means that patterns that require an implicit name will always have isInlineClass set to true, making this check seem unnecessary.

@k163377 k163377 force-pushed the optimize_findImplicitPropertyName branch from f4a93b6 to 5c675f1 Compare August 21, 2021 03:18
@k163377
Copy link
Contributor Author

k163377 commented Sep 29, 2021

@dinomite
This change will greatly improve serialization performance, so if possible, merge it in time for 2.13.

@dinomite
Copy link
Member

GitHub merged this but thinks it didn't ¯_(ツ)_/¯

@dinomite dinomite closed this Oct 15, 2021
dinomite added a commit that referenced this pull request Oct 15, 2021
Optimize `KotlinNamesAnnotationIntrospector.findImplicitPropertyName` method.
@k163377
Copy link
Contributor Author

k163377 commented Oct 15, 2021

@dinomite It seems that the wrong branch has been created, so please delete it.
https://github.com/FasterXML/jackson-module-kotlin/tree/optimize_findImplicitPropertyName

@k163377 k163377 deleted the optimize_findImplicitPropertyName branch October 18, 2021 14:51
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.

None yet

2 participants