Fixed
Status Update
No update yet.
Comments
go...@jakewharton.com
Looks like this is done at HEAD. There's a Composition factory function overload that does not take a key and skips the Compositions map.
Is the intent to remove Compositions completely? I only ask because its map will have problems in Kotlin/Native...
so...@google.com
Adam, is there anything actionable left on this ticket?
ad...@google.com
Nope, we should be good here. Recomposers keep a record of known non-disposed compositions, there's a global record of active recomposers, but there's no WeakMap anymore. Everything is based on explicit disposal.
Description
The only way to create a
Compositionis through thecompositionForfactory which goes through a staticCompositionsobject which maintains a static weak map.Adam P has tentatively said that removing this was in the plans. This is mostly just a tracking bug. Bonus: This means the expect/actual for
WeakMapcan be removed.