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
It would be nice to remove reorder, shiftlocus and user level use of rebuild, and just use set for everything.
There are a few steps needed to make this possible:
set and unsafe_set are split so that set always fixes everything to match the change, like reordering the array if you do set(A; X=> ForwardOrdered). Then unsafe_set would never fix anything else in the object, and just change the thing you specify.
keywords to set work just like rebuild, but fix everything that needs to be fixed from the change. Keywords to unsafe_set are just rebuild.
Then rebuild is back to being an internal method, shiftlocus is gone as set(A, Center()) will just work, and we heavily document set and unsafe_set and make sure they always behave in intuitive ways.
The text was updated successfully, but these errors were encountered:
It would be nice to remove
reorder
,shiftlocus
and user level use ofrebuild
, and just useset
for everything.There are a few steps needed to make this possible:
set
andunsafe_set
are split so thatset
always fixes everything to match the change, like reordering the array if you doset(A; X=> ForwardOrdered)
. Thenunsafe_set
would never fix anything else in the object, and just change the thing you specify.set
work just likerebuild
, but fix everything that needs to be fixed from the change. Keywords tounsafe_set
are justrebuild
.Then
rebuild
is back to being an internal method,shiftlocus
is gone asset(A, Center())
will just work, and we heavily documentset
andunsafe_set
and make sure they always behave in intuitive ways.The text was updated successfully, but these errors were encountered: