IssueTracker

See attached project. This is a very barebones example, this observation came up in a very big and complex project. When I use Modifier.clickable{} on a component like Text, or Icon, or Card, etc, it is getting recomposed along with other recompositions rather than skipping this. As far as I understand the clickable composable did not change, so there should not be any recomposition happening. I do not know how much of a performance issue this is in a very complex scenario where a Lazycolumn with multiple clickable texts are being recomposed due to some numbers next to the clickable texts are updating every 10s.

A more real life example: have a list of 1-500 items, each of them have a clickable (underlined) text, that would show a popup, and a number. The clickable text is added due to the fact that the onClick and onLongClick on the entire item is already reserved for other actions. The numbers are being fetched every 10s from the API so they update the items accordingly. In this scenario the Text with clickable also gets recomposed when the number does, according to the LayoutInspector.

Android Studio Ladybug Feature Drop | 2024.2.2 Patch 1
Build #AI-242.23726.103.2422.13016713, built on February 5, 2025
Runtime version: 21.0.5+-12932927-b750.29 amd64
VM: OpenJDK 64-Bit Server VM by JetBrains s.r.o.
Toolkit: sun.awt.windows.WToolkit
Windows 11.0
Kotlin plugin: K2 mode (Beta)
GC: G1 Young Generation, G1 Concurrent GC, G1 Old Generation
Memory: 8192M
Cores: 20
Registry:
  ide.instant.shutdown=false
  ide.experimental.ui=true
  i18n.locale=
Non-Bundled Plugins:
  com.intellij.lang.jsgraphql (242.21829.3)
  com.apollographql.ijplugin (4.1.1)


agp = "8.8.1"
kotlin = "2.0.0"
coreKtx = "1.15.0"
junit = "4.13.2"
junitVersion = "1.2.1"
espressoCore = "3.6.1"
lifecycleRuntimeKtx = "2.8.7"
activityCompose = "1.10.0"
composeBom = "2024.04.01"