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
With #1902, we will have the ability to remove nodes and add them elsewhere without recreation. Thus, all moves can be synthesized as removes and adds. Since these are exceedingly rare in our experience, it may be worth removing them as a concept altogether.
At the very least, we can make it a default implementation on Widget.Children so that in places where we can efficiently perform moves you still can, but in the case where it's hard or impossible (e.g., our current LazyList design) you don't have to worry about it.
The text was updated successfully, but these errors were encountered:
With #1902, we will have the ability to remove nodes and add them elsewhere without recreation. Thus, all moves can be synthesized as removes and adds. Since these are exceedingly rare in our experience, it may be worth removing them as a concept altogether.
At the very least, we can make it a default implementation on
Widget.Children
so that in places where we can efficiently perform moves you still can, but in the case where it's hard or impossible (e.g., our currentLazyList
design) you don't have to worry about it.The text was updated successfully, but these errors were encountered: