This is a feature I wasn’t sure for a long time how best to tackle. It’s worth noting that an initial attempt at `IterExplorer` was based on the monad pattern, which turned out to be a mistake, since monads are more of an anti-pattern, than being genuinely useful. The actual use-case that made me reconsider such a feature it to build an seamlessly chained sequence from several iterators. It would be simple to develop a suitable utility as a stand-alone helper, yet it seemed worth the effort to integrate this into the `IterExplorer` ecosystem, due to the flexible automatic adaptation to iterable source pipelines provided therein. Going this route incurred some cost however, unveiling several defects related to handling nested iterable types in the generic processing framework.
12 MiB
12 MiB
| The file is too large to be shown. |