A modern programming language that makes developers happier.

kotlinlang

That seems to be a reasonable interpretation. However, as our measurements show, a changing key for `Grid` wouldn't make Compose throw away the old `Grid`'s content and rebuilt everything anew. I have even tried to use a separate counter as a grid ID, incrementing on each animation setting change, but that's still slower than not showing the grid for a period of time. I can only guess, but Compose seems to infer that while there is now a new `Grid`  (identified by a new key), its content has not actually changed (at least initially), so it just "moves" all of its Composables to the "new" `Grid`. Could someone from the Compose team enlighten us?