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

Fix casting issue #1084

Merged
merged 1 commit into from
Jan 11, 2024
Merged

Fix casting issue #1084

merged 1 commit into from
Jan 11, 2024

Conversation

dmlloyd
Copy link
Contributor

@dmlloyd dmlloyd commented Jan 10, 2024

In IntelliJ, the existing combination of raw types, casting, and lambdas often produces spurious compilation errors. This PR introduces a solution which hides the unsafe cast in a single method, and also uses Map.putIfAbsent to avoid constructing a lambda for this case.

In IntelliJ, the existing combination of raw types, casting, and lambdas often produces spurious compilation errors. This PR introduces a solution which hides the unsafe cast in a single method, and also uses `Map.putIfAbsent` to avoid constructing a lambda for this case.
@radcortez radcortez merged commit 883c97f into smallrye:main Jan 11, 2024
8 checks passed
@github-actions github-actions bot added this to the 3.5.2 milestone Jan 11, 2024
@dmlloyd dmlloyd deleted the casting branch January 11, 2024 13:31
radcortez pushed a commit that referenced this pull request Jan 11, 2024
In IntelliJ, the existing combination of raw types, casting, and lambdas often produces spurious compilation errors. This PR introduces a solution which hides the unsafe cast in a single method, and also uses `Map.putIfAbsent` to avoid constructing a lambda for this case.
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