Repository navigation
We want design parity with FSharp.Control.AsyncSeq #345
Copy link
Copy link
Closed
Labels
enhancementNew feature or requestNew feature or request
Description
Activity
github-actions commented
on Mar 14, 2026 on Mar 14, 2026 – with GitHub Actions · Hidden as outdatedshow commentMore actions- added a commit that references this issue
on Mar 15, 2026 /repo-assist work on group 1
Reacted by github-actions- added a commit that references this issue
on Mar 17, 2026 github-actions commented
on Mar 17, 2026 on Mar 17, 2026 – with GitHub ActionsContributorMore actionsPull request created: #349
Generated by Repo Assist
- added a commit that references this issue
on Mar 17, 2026 github-actions commented
on Mar 17, 2026 on Mar 17, 2026 – with GitHub ActionsContributorMore actionsPull request created: #350
Generated by Repo Assist
github-actions commented
on Mar 17, 2026 on Mar 17, 2026 – with GitHub ActionsContributorMore actions🤖 This is an automated response from Repo Assist.
As requested, I've implemented all Group 1 functions from the AsyncSeq design-parity gap analysis. Draft PR created: [Repo Assist] feat: add Group 1 AsyncSeq design-parity functions (branch:
repo-assist/fix-issue-345-group1-20260317).Functions added
Function Description replicateInfiniteInfinite sequence repeating a constant value replicateInfiniteAsyncInfinite sequence from an async thunk replicateUntilNoneAsyncSequence from async thunk, stops on NonefirstOrDefaultFirst matching element or default lastOrDefaultLast matching element or default splitAtSplit prefix of N elements from remainder zipWith/zipWithAsyncZip two sequences with a mapping function zipWith3/zipWithAsync3Zip three sequences with a mapping function chunkBy/chunkByAsyncChunk consecutive elements with equal keys threadState/threadStateAsyncStateful map threading state through sequence Note:
distinctUntilChangedWith/distinctUntilChangedWithAsyncare in separate PR #346.Test status
✅ Build: 0 warnings, 0 errors
✅ Format: clean
✅ Tests: 4,942 passed, 2 skipped (infrastructure), 0 failed
326 new tests across 6 new test filesGenerated by Repo Assist for issue #345 · ◷
To install this agentic workflow, run
gh aw add githubnext/agentics/workflows/repo-assist.md@346204513ecfa08b81566450d7d599556807389f
Metadata
Metadata
Assignees
Labels
enhancementNew feature or requestNew feature or request
/repo-assist We want design parity between FSharp.Control.AsyncSeq and FSharp.Control.TaskSeq.
https://github.com/fsprojects/FSharp.Control.AsyncSeq
One difference is withCancellation is missing from FSharp.Control.AsyncSeq but more research about reaching design parity is needed. Look into what's needed for TaskSeq here.