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

ExceptionHandlingFlowContext: use java.util.IdentityHashMap #3426

Merged
merged 1 commit into from
Dec 11, 2024

Conversation

jukzi
Copy link
Contributor

@jukzi jukzi commented Dec 9, 2024

  • avoids raw types
  • deletes custom ObjectCache

ObjectCache implemented a HashMap using hashCode() but not equals(). Instead it used == identity. JDK offers a special Map for identity since 1.4, consistently using System.identityHashCode().

relates to #3412

* avoids raw types
* deletes custom ObjectCache

ObjectCache implemented a HashMap using hashCode() but not equals().
Instead it used == identity. JDK offers a special Map for identity since
1.4, consistently using System.identityHashCode().

relates to eclipse-jdt#3412

Also solved follow up
* LambdaExpression "Redundant specification of type arguments"
@jukzi jukzi force-pushed the ExceptionHandlingFlowContext branch from 110945d to bad35f0 Compare December 10, 2024 07:11
@srikanth-sankaran
Copy link
Contributor

Thanks @juzki I will review these tomorrow

Copy link
Contributor

@srikanth-sankaran srikanth-sankaran left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Changes look good to me.

@jukzi
Copy link
Contributor Author

jukzi commented Dec 11, 2024

@srikanth-sankaran thanks for review.

@jukzi jukzi merged commit b718fe6 into eclipse-jdt:master Dec 11, 2024
10 checks passed
@jukzi jukzi deleted the ExceptionHandlingFlowContext branch December 11, 2024 09:31
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.

3 participants