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

ECJ emits different inner class references for the same code #1635

Merged
merged 2 commits into from
Nov 29, 2023

Conversation

srikanth-sankaran
Copy link
Contributor

@srikanth-sankaran srikanth-sankaran commented Nov 28, 2023

What it does

Converge divergent signature management routines ensuring that we track nested member type references uniformly.
Fixes #1631

Author checklist

@srikanth-sankaran srikanth-sankaran linked an issue Nov 28, 2023 that may be closed by this pull request
@srikanth-sankaran srikanth-sankaran changed the title Regression test that demonstrates current behavior Different inner class references generated for same code Nov 29, 2023
@srikanth-sankaran srikanth-sankaran self-assigned this Nov 29, 2023
@srikanth-sankaran srikanth-sankaran marked this pull request as ready for review November 29, 2023 06:54
@srikanth-sankaran srikanth-sankaran added this to the 4.31 M1 milestone Nov 29, 2023
@srikanth-sankaran srikanth-sankaran changed the title Different inner class references generated for same code ECJ emits different inner class references generated for same code Nov 29, 2023
@srikanth-sankaran srikanth-sankaran changed the title ECJ emits different inner class references generated for same code ECJ emits different inner class references for the same code Nov 29, 2023
@srikanth-sankaran srikanth-sankaran merged commit bbe1806 into eclipse-jdt:master Nov 29, 2023
4 of 6 checks passed
@srikanth-sankaran srikanth-sankaran deleted the GH1631 branch November 29, 2023 09:23
@iloveeclipse
Copy link
Member

image

@srikanth-sankaran : please next time avoid merging PR's that show errors. I know there are sometimes "checks" that are red without a good reason, but in general we are trying to keep the status green and so if anything is red it is most likely a sign of a problem with the PR. In doubt please just ask.

@srikanth-sankaran
Copy link
Contributor Author

@iloveeclipse I restarted the tests a couple of times only for the symptoms of the failing checks to shift around.

I consulted with @jarthana and he asked me to go ahead since it "looks like the previous PRs that went in had the same problem." (Private chat)

FWIW

@srikanth-sankaran
Copy link
Contributor Author

@iloveeclipse I restarted the tests a couple of times only for the symptoms of the failing checks to shift around.

I consulted with @jarthana and he asked me to go ahead since it "looks like the previous PRs that went in had the same problem." (Private chat)

FWIW

Ah, I see that what I took to be a temporary process glitch caused some grief around bundle numbers. Sorry about that!

@jarthana
Copy link
Member

Oops! Sorry for the wrong and admittedly lazy advice. Off topic, it will be helpful if the failure reason (the version update) reported prominently rather then being buried in the log.

rgrunber pushed a commit to eclipse-jdtls/eclipse-jdt-core-incubator that referenced this pull request Jan 9, 2024
…-jdt#1635)

* Extract signature computation into a method of its own; Ensure nested
type references are tracked properly
* Fixes eclipse-jdt#1631
robstryker pushed a commit to robstryker/eclipse.jdt.core that referenced this pull request Jul 18, 2024
…-jdt#1635)

* Extract signature computation into a method of its own; Ensure nested
type references are tracked properly
* Fixes eclipse-jdt#1631
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.

Different inner class references generated for same code
3 participants