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
I haven't really thought very hard about this, but it seems like it should be possible to create a call function which takes as its first argument a recipe name, and then invokes that recipe with some arguments, and returns whatever that recipe writes to standard out:
I'm sure there are tons of weird considerations and edge cases, like what if a recipe depends on a variable whose value depends on an invocation of call. In that particular case though, this is the same kind of loop detection that we already do for variables and recipe dependencies, and if all calls to call are statically resolvable (which they should be), then we could detect this easily.
I haven't really thought very hard about this, but it seems like it should be possible to create a
call
function which takes as its first argument a recipe name, and then invokes that recipe with some arguments, and returns whatever that recipe writes to standard out:This could also be used to evoke recipes in the middle of other recipes:
Without needing to recursively invoke
just
.The text was updated successfully, but these errors were encountered: