forked from eclipse-jdt/eclipse.jdt.core
-
Notifications
You must be signed in to change notification settings - Fork 1
Restore comparingsearch level #1546
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
Open
mickaelistria
wants to merge
1,323
commits into
eclipse-jdtls:dom-with-javac
Choose a base branch
from
mickaelistria:restore-comparingsearch-level
base: dom-with-javac
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Restore comparingsearch level #1546
mickaelistria
wants to merge
1,323
commits into
eclipse-jdtls:dom-with-javac
from
mickaelistria:restore-comparingsearch-level
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
22c76b5 to
31ed617
Compare
|
I'd like to see failures down a bit more before we go doing this, but it's ultimately up to you. |
Author
|
I agree, I was expecting a bit less than a hundred failures, but it's much more. I am targetting a merge when the extra failures are up by 100 or less. |
999cd3e to
bf60323
Compare
73d28b4 to
aa8f401
Compare
4082278 to
ebc593c
Compare
Signed-off-by: Rob Stryker <[email protected]>
Signed-off-by: Rob Stryker <[email protected]>
Signed-off-by: Rob Stryker <[email protected]>
eg. there should be no keywords when completing at the `|`
```java
int[] a = new int[] { | };
```
Signed-off-by: David Thompson <[email protected]>
Fixes eclipse-jdtls#1394 Fixes eclipse-jdtls#1395
Instead of always re-reading the jars for symbols, we create a local cache that is capable of recreating the symbol into any context reliably enough from memory. This should drastically improve performance.
* ForAll/generic methods
* Synchronize init of reflection * Do not share the signatureBuffer, keep it instance specific to avoid concurrent modification. Sharing doesn't bring any benefit anyway.
A parser may decide to keep a TextElement as " blah" with (offset, length)=(N,5); or as "blah" with (offset,length)=(N+1,4). Both are valid. Make test tolerate both.
The parent EnumConstantDeclaration is already checked, no need to re-check the name.
I disagree personally but this is what JDT does. Signed-off-by: David Thompson <[email protected]>
11c94f4 to
99440ba
Compare
Another portion of the fix depended on addressing eclipse-jdt#4247, which is now resolved Signed-off-by: David Thompson <[email protected]>
There are other issues that arise when having a `module-info.java` in a Java 8 project, but this makes sure that we at least don't try to convert the AST nodes, which prevents an exception. Fixes eclipse-jdt#193 Signed-off-by: David Thompson <[email protected]>
Record components are often modeled as ILocalVariable, which might use different parent in a case or another. Instead of strictly checking for equal model element, we check that they are equivalent (name and position)
eg. after `|`
```java
public class CompleteInInstanceof {
public void myMethod() {
Object o = null;
boolean a = o instanceof RequiresDirective requires && useRequiresDirective(req|);
}
static class RequiresDirective {
private int a;
public RequiresDirective(int a) { this.a = a; }
int getA() { return a; }
}
public static boolean useRequiresDirective(RequiresDirective requiresDirective) {
return requiresDirective.getA() > 5;
}
}
```
Fixes eclipse-jdt#1593
Signed-off-by: David Thompson <[email protected]>
Completion tests are currently ignored as functional coverage for completion is already good and many tests are really failing for insignificant details (such as relevance which is overridden in UI anyway). So we skip the test to avoid noise and let dogfooding and actual usage feedback drive further improvements to completion. We may re-enable those tests later.
bf60323 to
20c5769
Compare
Author
|
Adds ~200 failures, let's wait a bit before merging it. |
6dc0d95 to
25a5a08
Compare
b1b4e0e to
309f390
Compare
685330d to
959d707
Compare
2dbfcc7 to
6e1fd32
Compare
0b01689 to
87ead9e
Compare
6d23874 to
c8f8d92
Compare
055e846 to
18452eb
Compare
411dfec to
ac3eb19
Compare
5738537 to
9962d57
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.