You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Look at the anxious section at the end of the original Compose integration writeup. We mainly rationalized passing ViewEnvironment around because it was so fragile WRT ViewRegistry -- things would blow up if there was no ViewRegistry in ViewEnvironment, that kind of thing.
This is no longer the case. ViewRegistry is very much optional, and having a missing or empty one is just fine. And the manually passed ViewEnvironment has been a chronic optmization problem. Maybe we should undo that decision, and make ViewEnvironment just another Compose local.
Look at the anxious section at the end of the original Compose integration writeup. We mainly rationalized passing
ViewEnvironment
around because it was so fragile WRTViewRegistry
-- things would blow up if there was noViewRegistry
inViewEnvironment
, that kind of thing.This is no longer the case.
ViewRegistry
is very much optional, and having a missing or empty one is just fine. And the manually passedViewEnvironment
has been a chronic optmization problem. Maybe we should undo that decision, and makeViewEnvironment
just another Compose local.The text was updated successfully, but these errors were encountered: