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

Issue #12809: Improve performance of lambda processing #12814

Merged
merged 1 commit into from
Mar 18, 2023

Conversation

@rnveach rnveach marked this pull request as draft March 10, 2023 14:53
@nrmancuso nrmancuso force-pushed the issue-12809 branch 2 times, most recently from cd00ad3 to 26f5021 Compare March 12, 2023 14:47
@rnveach
Copy link
Member

rnveach commented Mar 12, 2023

@nrmancuso should we developer our own certified method of testing performance?

Ex: https://github.com/rnveach/checkstyle/commits/more_audits

@nrmancuso nrmancuso force-pushed the issue-12809 branch 2 times, most recently from ec8d60e to 63c0e0d Compare March 16, 2023 19:35
@dreis2211
Copy link

@nrmancuso I find it hard to see if there is anything changing when you force-push. Should I retest this? And is there anything missing that blocks this from moving out of the Draft status?

@nrmancuso
Copy link
Member Author

@dreis2211 you are good, next step for you is to use it after we release :) I have some reports to generate and share and a few other odds and ends here.

@nrmancuso nrmancuso force-pushed the issue-12809 branch 2 times, most recently from 52c5fa9 to a4ed3fc Compare March 17, 2023 18:42
@nrmancuso
Copy link
Member Author

@dreis2211 this should be final iteration of code, feel free to test for performance again

@nrmancuso should we developer our own certified method of testing performance?

@rnveach this is a good idea, but I am not sure how to execute it. When I make grammar changes, I sometimes analyze the grammar using the ANTLR tool, but from a holistic perspective, I am not sure how to do this.

@nrmancuso nrmancuso requested review from dreis2211, romani and rnveach and removed request for dreis2211 March 18, 2023 02:21
* The tokens here are technically expressions, but should
* not return an EXPR token as their root.
*/
private static final int[] EXPRESSIONS_WITH_NO_EXPR_ROOT = {
Copy link
Member Author

Choose a reason for hiding this comment

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

Made this a static field so that we do not have to create array with each method call.

private DetailAstImpl buildExpressionNode(ParseTree exprNode) {
final DetailAstImpl expression = visit(exprNode);

final DetailAstImpl exprRoot;
Copy link
Member Author

Choose a reason for hiding this comment

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

Cleaned up this code a bit, but this is basically what was in the visitExpression method.

@nrmancuso nrmancuso marked this pull request as ready for review March 18, 2023 02:25
@dreis2211
Copy link

dreis2211 commented Mar 18, 2023

Performance looks good still @nrmancuso

@rnveach rnveach assigned romani and unassigned rnveach Mar 18, 2023
Copy link
Member

@romani romani left a comment

Choose a reason for hiding this comment

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

ok to merge

@romani romani merged commit 258c792 into checkstyle:master Mar 18, 2023
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.

Improve performance of lambda processing
4 participants