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
Just to think over what would happen if users start to use delayed a la carte:
mapvalues -- returning delayed(f)(x) is completely OK. The chaining of lazy values should work as expected. Calling delayed functions with other values which may themselves be delayed is OK. But calling it with say an array of delayed values is not.
mapsubtrees -- returning delayed(f)(x) will work but not when f(x) is a FileTree. However, a FileTree with delayed values is OK.
Just to think over what would happen if users start to use
delayed
a la carte:mapvalues
-- returningdelayed(f)(x)
is completely OK. The chaining of lazy values should work as expected. Callingdelayed
functions with other values which may themselves bedelayed
is OK. But calling it with say an array of delayed values is not.mapsubtrees
-- returningdelayed(f)(x)
will work but not whenf(x)
is a FileTree. However, a FileTree withdelayed
values is OK.reducevalues
-- seems fine again. as in 1.cc @DrChainsaw
The text was updated successfully, but these errors were encountered: