Disable expensive LambdaMethodReference by default #2999
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.
See #2997
LambdaMethodReference is incredibly expensive, even compared to log safety flow analysis! It was originally added to clean up the results of other excavators, not to prevent runtime failures. We will apply the cleanup asynchronously via an excavator, rather than on a per-compilation basis, delayed fixups are a reasonable tradeoff here to dramatically improve compilation performance.
While we could move the code entirely into excavator instead of maintaining it here, however that has some risk for folks who explicitly configure/disable the
LambdaMethodReference
check (specifically, they would fail with:LambdaMethodReference not a valid checker name
)==COMMIT_MSG==
Disable expensive LambdaMethodReference by default
==COMMIT_MSG==