IssueTracker

I don't think the average developer understands the distinction between method references and method definitions in this context (inside a DEX file). I know I don't.

@jvg, can you elaborate?

people who are looking at the bytecode in the dex to optimize their app through shrinking hopefully will learn the difference as string tables for method references between various dex files can account for quite a bit of disk space. but more importantly a definition is something you can analyze its code for where a reference you can't so the UI can be confusing without seeing the difference

How about something like this?

I think having defined members be directly under the class node while references are nested in a group makes more sense.

Also note that the method refs have a slightly different icon. There is no existing equivalent for field refs that I could find.

https://screenshot.googleplex.com/4yXVM9Rzh4wnkjM.png

sounds reasonable to me, thanks

Thank you for your patience while our engineering team worked to resolve this issue. A fix for this issue is now available in:

• Android Studio Ladybug Feature Drop | 2024.2.2 Canary 4
• Android Gradle Plugin 8.8.0-alpha04

We encourage you to try the latest update.

If you notice further issues or have questions, please file a new bug report.

Thank you for taking the time to submit feedback — we really appreciate it!

I don't see what changed in this space between 1.9.20 and 2.0.20

One major change between two is whether K2 Lint is used by default or not, and I remember there was/is an issue about binary resolution, in particular, when there are synthetic parameters generated by Compose compiler plugin. I'm not entirely sure it's properly addressed at that time or it still remains.

I remember there was/is an issue about binary resolution, in particular, when there are synthetic parameters generated by Compose compiler plugin.

I meant this one: b/328119668 (and https://youtrack.jetbrains.com/issue/KT-66592), and it's still reproducible in ToT. :'(

As a note, reproduced (thanks!):

.../ComposeLint86/ComposeLint86/app/src/main/java/com/example/composelint86/MainActivity.kt:35: Error: produceState calls should assign value inside the producer lambda [ProduceStateDoesNotAssignValue from androidx.compose.runtime]
      val state = produceState("No-one", key1 = Unit) {
                  ~~~~~~~~~~~~
  
     Explanation for issues of type "ProduceStateDoesNotAssignValue":
     produceState returns an observable State using values assigned inside the
     producer lambda. If the lambda never assigns (i.e value = foo), then the
     State will never change. Make sure to assign a value when the source you
     are producing values from changes / emits a new value. For sample usage see
     the produceState documentation.
  
     Vendor: Jetpack Compose
     Identifier: androidx.compose.runtime

It's supposed to be:

@Composable
fun <T> produceState(
    initialValue: T,
    key1: Any?,
    producer: suspend ProduceStateScope<T>.() -> Unit
): State<T> { ... }

but resolved to:

@Composable
fun <T> produceState(
    initialValue: T,
    producer: suspend ProduceStateScope<T>.() -> Unit
): State<T> { ... }

FYI, another instance of wrong resolution: b/371686443.

Tested on the attached project (in comment#4) with AGP 8.8.0-alpha09 and gradle-8.10.2-bin.zip