Open felixfbecker opened 7 years ago
Actually, that was my idea creating a pr, after the pr has been merged. But you are stealing my ideas constantly. :D
Well, go ahead. Don't let me keep you :)
@roblourens Are you fine with this change? I would start getting on this.
@jens1o Already almost finished ;)
Sorry, so you had implemented that already? Okay. Then I search for other things :D
PHP has native interfaces and classes for Iterators (
Generator
implementsIterator
). Iterators can be traversed withforeach
and composed easily, for example by filtering throughCallbackFilterIterator
.In particular, it has the
RecursiveIterator
interface, that adds two more methods to implement:hasChildren()
andgetChildren()
. This allows it to be traversed with aRecursiveIteratorIterator
, which has countless options for emitting all nodes or just leaves, using level order, etc.ParentIterator
can be used to visit just nodes with child nodes,RecursiveLimitIterator
to limit the nodes traversed,AppendIterator
to concatenate Iterators,RecursiveTreeIterator
can be used to draw an ASCII tree of an AST andRecursiveCallbackFilterIterator
to filter nodes (including skipping children). Really a lot of awesome stuff in there.The Parser already uses Generators for traversal, which is great, but it only has limited options for filtering and skipping certain children through a callback: https://sourcegraph.com/github.com/Microsoft/tolerant-php-parser/-/blob/src/Node.php#L158-159 I think providing class-based implementations for Iterators would give greater flexibility.