-
Notifications
You must be signed in to change notification settings - Fork 434
KT-22210 Use meaningful parameter names instead of p0
#464
Comments
Is this because gradle is compiled without the https://docs.oracle.com/javase/tutorial/reflect/member/methodparameterreflection.html I can open a pull request if this seems like an appropriate fix. |
|
@eskatos I searched Kotlin's issue tracker but couldn't find this specific problem. Was it reported? |
@AlexCzar not that I know of, feel free to report it upstream, I'll get back to it next week if you don't beat me to it. It doesn't happen when no |
p0
p0
Reported upstream: https://youtrack.jetbrains.com/issue/KT-22210 |
Moved to backlog so we can decide if we should tackle it ourselves. |
Two candidate solutions until Gradle is built with Java 8 and
|
Tracked it down to https://youtrack.jetbrains.com/issue/KT-25193 |
Good find! |
A workaround is mentioned in https://youtrack.jetbrains.com/issue/KT-25193#comment=27-2957572
Description of that argument is |
Made an attempt with |
Adding To make all this work we'd need the Gradle API jar bytecode to include parameter names. |
🎆 🎉 👍 🎉 🎆 |
In IntelliJ IDEA, when you enable the option that displays implicit parameter names, you get weird
p0
parameters inid()
andplugin()
. Meaningful parameter names would be better.The text was updated successfully, but these errors were encountered: