-
Notifications
You must be signed in to change notification settings - Fork 743
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
Limitation of InlineMeInliner with lambda expressions #2347
Comments
The unit test doesn't get refactored because the check uses
I think this might be a known limitation of the handling of lambdas. The original issue might be separate. Was the latest version of the |
#2347 PiperOrigin-RevId: 374794248
#2347 PiperOrigin-RevId: 374915809
The crash should be fixed by dc7252b. I'll keep this open to track #2347 (comment). |
Few updates:
It's not in Note that we fork |
Description of the problem / feature request:
I am seeing the following crash on
InlineMeInliner
for Error Prone 2.7.1.This is on code edited after simply following the suggestions of
InlineMeSuggester
:Code samples below (identifier names changed, but AST structure is similar).
This gets reported on the call-site for:
Where that version of
client(...)
has been@Deprecated
and marked with@InlineMe
as follows:I can confirm, stepping through the build with a debugger, that when this line is hit when processing
imports={"com.example.Client"}
,a.type
happens to beBottomType
/<nulltype>
(even though the value does show an array containing the string"com.example.Client"
). We are using the EP javac on a JDK 8 JVM.Bugs: what's the simplest, easiest way to reproduce this bug? Please provide a minimal example if possible.
I tried to make a repro case as a test case for Error Prone here, but while there is indeed a problem in that the rewriting doesn't happen (and thus the test fails), it doesn't crash with the same exception. I'll be working on a stand alone project gradle that attempts to show the issue without our build system in the way and update this issue if that works.
What version of Error Prone are you using?
2.7.1
Have you found anything relevant by searching the web?
Nothing that quite matches, either as an Error Prone or a JDK bug.
The text was updated successfully, but these errors were encountered: