🚀 go-pugleaf

CLU's explicit concept of iterators seems at the first glance preferable
to the rather ad hoc way iterators are defined in oo -languages. (As
a method of an object, or as a friend-class.) Instead of handling
the whole state of the iterator explicitely, one can imagine the yield
statement as yust a "print" statement which will pe "piped" to the caller.
But this works for simple examples only. If you want to traverse e.g. a binary
tree you have to call within the iterator the same iterator for both left and
right subtree. In my opinion it would be more intuitive to use the "print"
methapher for all kinds of calls.

Has there anybody extended iterators in such a way?

Ulrich