Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
There are a few reasonable ways recurse could behave. The standard libraries implemntation does the following: `recurse(f;cond)` yields ., then . | f if . | f satisfies cond, then . | f | f if . | f | f satisfies cond, etc... But it turns out that for paths, you want the following behavior: `recurse(f;cond)` yields ., then . | f is . satisfies cond, then . | f | f if . | f satisfies cond, etc. The difference is non-trivial (and there are actually a few degrees of freedom here), so I gave paths its own definition, rather than adding a new builtin. This means we don't have two builtin recurses floating around.
- Loading branch information