Add defdata patterns and operations for Iterables and Iterators
#295
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
2 tasks
jfeser
approved these changes
Jun 27, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Factored out of #289 into a standalone PR, and not blocked by it or #288.
This PR adds a higher-order operation
defstream, two operationsiter_andnext_anddefdatarules forIterableandIterator, the minimal API required for reinterpreting stream iteration. It does not add adeftermrule, which is the real substance of #288 and #289.defstream(renamed from #289'sforexpr) takes a body expression and a named collection ofIterable-typedTerms, much like Python'sast.GeneratorExp. It is the correct target for #289's syntax transformations of generator expressions toeffectfulTerms