Use ASTProvider to getAST for source action handlers #1533
Merged
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.
Signed-off-by: Jinbo Wang jinbwan@microsoft.com
ASTProvider will cache the AST node for the active editor, should use it whenever possible.
Below is the profiling comparison on editing a Java file with 200 LOC.
Before:
The source action handlers will parse a new AST every time in the source action handler. Most of time of getSourceActionCommands is on parsing AST node. And the time ratio between getSourceActionCommands and getCodeActionCommands is about 64%.
After:
Use ASTProvider to get AST node, and the time ratio reduces to 40%.