-
Notifications
You must be signed in to change notification settings - Fork 118
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
Remove AbstractUnnamedTypeDeclaration
#2483
Remove AbstractUnnamedTypeDeclaration
#2483
Conversation
@jarthana , @stephan-herrmann : tomorrow is RC1 build. It would be very helpful to review (and merge?) this PR ASAP to avoid last minute fixes in RC2. |
org.eclipse.jdt.core/dom/org/eclipse/jdt/core/dom/AbstractTypeDeclaration.java
Outdated
Show resolved
Hide resolved
I am told @jarthana is on leave till Monday. I will study this and share my comments. @mpalat has also offered to look into this - Thanks! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Basically looks good, the issue of calling preLazyInit()
, postLazyInit()
has priority among my remarks.
Let's wait for at least one more review.
org.eclipse.jdt.core/dom/org/eclipse/jdt/core/dom/DefaultBindingResolver.java
Show resolved
Hide resolved
org.eclipse.jdt.core/dom/org/eclipse/jdt/core/dom/DefaultBindingResolver.java
Outdated
Show resolved
Hide resolved
org.eclipse.jdt.core/dom/org/eclipse/jdt/core/dom/ImplicitTypeDeclaration.java
Outdated
Show resolved
Hide resolved
org.eclipse.jdt.core/dom/org/eclipse/jdt/core/dom/ImplicitTypeDeclaration.java
Outdated
Show resolved
Hide resolved
org.eclipse.jdt.core/dom/org/eclipse/jdt/core/dom/ImplicitTypeDeclaration.java
Outdated
Show resolved
Hide resolved
That requires some reverts in JDT/UI, right? Should those be prepared already? |
Not reverts but careful changes, as some logic changed too => eclipse-jdt/eclipse.jdt.ui#1420 |
Sorry I should have prepared a PR with the required changes to jdt.ui, my bad I'll have that up soon too |
See eclipse-jdt/eclipse.jdt.core#2483 Signed-off-by: David Thompson <davthomp@redhat.com>
No problem, but you can review eclipse-jdt/eclipse.jdt.ui#1420 |
Looking into test failures |
They are legitimate, working on a fix |
I can't reproduce the failure ( |
69c2f23
to
106a134
Compare
AbstractUnnamedTypeDeclaration
AbstractUnnamedTypeDeclaration
org.eclipse.jdt.core/dom/org/eclipse/jdt/core/dom/ImplicitTypeDeclaration.java
Outdated
Show resolved
Hide resolved
- rework hierarchy so ImplicitTypeDeclaration depends directly on AbstractTypeDeclaration - use subclass of `SimpleName` "EmptyName" as the `typeName` for `ImplicitTypeDeclaration`, since `SimpleName` cannot have the empty string as the type name - delete AbstractUnnamedTypeDeclaration - revert AbstractTypeDeclaration to pre-ImplicitTypeDeclaration - reincorporate Jörg's fix in AbstractTypeDeclaration that makes `typeName` volatile Signed-off-by: David Thompson <davthomp@redhat.com>
106a134
to
709b674
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If build succeeds, this is good to go from my p.o.v.
thanks
I'm going to sleep now. If you are going to merge this, please also merge eclipse-jdt/eclipse.jdt.ui#1420 at same time, even if it doesn't compile yet on jenkins, it compiles with this PR. Merging only this PR will break the SDK build. |
@stephan-herrmann @datho7561 Since this is still a preview feature, an "@noreference" to the ImplicitTypeDeclaration is the norm we follow - until it becomes a standard feature. So I would request to add that in the JavaDoc before merging |
@mpalat : I think David can add annotation for the next build. I would like to have all ready for RC1 now, so we can run all tests etc. |
@iloveeclipse - yes, that's sounds fine. |
See eclipse-jdt#2483 (comment) Signed-off-by: David Thompson <davthomp@redhat.com>
See #2483 (comment) Signed-off-by: David Thompson <davthomp@redhat.com>
What it does
See #2481
ImplicitTypeDeclaration
depends onAbstractTypeDeclaration
ImplicitTypeDeclaration
as suggested by StepheninternalResolveBinding()
forImplicitTypeDeclaration
AbstractTypeDeclaration
to how it was beforeImplicitTypeDeclaration
was addedtypeName
volatileAbstractUnnamedTypeDeclaration
How to test
See #2481, it should fix pasting snippets into the package explorer (
it doesn't yet, it needs work, currently it throws an "Invalid identifier" exception).Author checklist