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

Config lambda fix #667

Merged
merged 2 commits into from
Aug 30, 2023
Merged

Config lambda fix #667

merged 2 commits into from
Aug 30, 2023

Conversation

kilink
Copy link
Member

@kilink kilink commented Aug 30, 2023

No description provided.

For no-arg and single-arg default config methods, use LambdaMetafactory to generate
Function and BiFunction accessors instead of going through the MethodHandle directly,
which avoids some overhead.
Generating config proxies would break if the supplied interface inherited from
another interface with a default method; this was due to the wrong type being
supplied to the LambdaMetafactory in asFunction / asBiFunction. Switch to
using the type from the MethodHandle instead of the Method.

Additionally, add a test case that covers this scenario.
@rgallardo-netflix rgallardo-netflix merged commit 6b4b915 into 2.x Aug 30, 2023
2 checks passed
@rgallardo-netflix rgallardo-netflix deleted the config-lambda-fix branch May 22, 2024 18:20
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