Skip to content

Conversation

@mickaelistria
Copy link
Contributor

Through ASTParser.

What it does

The ASTParser implementation may trigger extra analysis on demand. The FORCE_PROBLEM_DETECTION flag must be somehow passed to underlying ICompilationUnitResolver implementation to allow that.

Fixes #4631

How to test

See it in combination with eclipse-jdtls#1879 which clarifies that this flag is necessary to make some tests pass with a DOM-based approach.

Author checklist

Through ASTParser.
The ASTParser implementation may trigger extra analysis on demand. The
FORCE_PROBLEM_DETECTION flag must be somehow passed to underlying
ICompilationUnitResolver implementation to allow that.

Fixes eclipse-jdt#4631
@mickaelistria
Copy link
Contributor Author

@rgrunber @jjohnstn @datho7561 Could any of you review (snd merge if appropriate) this path?

@mickaelistria
Copy link
Contributor Author

This addition would have a huge impact on the Javac integration (boosting both correctness and performance), and has no effect on the regular execution flow. The proposed API is (IMO) very safe.
So I would be grateful if this could be considered for RC1.

Copy link
Contributor

@jjohnstn jjohnstn left a comment

Choose a reason for hiding this comment

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

+1

@jjohnstn jjohnstn merged commit 745799b into eclipse-jdt:master Nov 18, 2025
13 checks passed
@mickaelistria
Copy link
Contributor Author

Thank you!

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.

ASTParser misses support for ICompilationUnit.FORCE_PROBLEM_DETECTION

3 participants