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's pretty common to stack chooser funcs on top of a fallback that just tries to use basicnode.Prototype.Any. If we defined a nice API for this, then the user could do:
We could bikeshed on the name: Chooser, DefaultChooser, FallbackChooser. I think just "Chooser" is nice because it does just that - people could use it in a number of ways, it doesn't need to be a fallback or everyone's default.
The text was updated successfully, but these errors were encountered:
I keep seeing code like:
It's pretty common to stack chooser funcs on top of a fallback that just tries to use
basicnode.Prototype.Any
. If we defined a nice API for this, then the user could do:We could bikeshed on the name:
Chooser
,DefaultChooser
,FallbackChooser
. I think just "Chooser" is nice because it does just that - people could use it in a number of ways, it doesn't need to be a fallback or everyone's default.The text was updated successfully, but these errors were encountered: