mcpiroman
12/06/2021, 5:33 PMandroidx.compose.runtime
- mostly methods like ComposerImpl.end
, ComposerImpl.comsume
, SlotTable.access
. All other modules like layout, measuring, rendering seem to be OK (except for `Composer.materialize`which is also a very hot path).
What do I do - I have simply a Column of like 400 elements, which frankly is not that lot. No LazyColumn because it is even slower and secondly I have to have all the elements instantiated.
It is about CfD so I don't have separate release build. (I did manage to get rid of all `sourceInformation-`calls though which did not help much.)Chuck Jazdzewski [G]
12/06/2021, 7:31 PMmcpiroman
12/06/2021, 8:04 PMif(map.contains(key)) map.get(key)
.Chuck Jazdzewski [G]
12/06/2021, 11:26 PMresolveCompositionLocal
which could be improved a bit to avoid the second lookup.mcpiroman
12/23/2021, 7:15 PMresolveCompositionLocal
.
But generally, couldn't e.g. each group have it's own copy of the composition local map, instead of traversing upwards to find it? It's PersistentMap after all so it can be mostly the same shared instance and lookup seems much more common than providing new locals.Chuck Jazdzewski [G]
12/27/2021, 11:08 PM