Skip to content

[Repo Assist] Add AsyncSeq.distinct, distinctBy, distinctByAsync, countBy, countByAsync, exactlyOne, tryExactlyOne #130

[Repo Assist] Add AsyncSeq.distinct, distinctBy, distinctByAsync, countBy, countByAsync, exactlyOne, tryExactlyOne

[Repo Assist] Add AsyncSeq.distinct, distinctBy, distinctByAsync, countBy, countByAsync, exactlyOne, tryExactlyOne #130

Triggered via pull request February 24, 2026 12:24
Status Success
Total duration 1m 35s
Artifacts

pull-request.yml

on: pull_request
Fit to window
Zoom out
Zoom in

Annotations

4 warnings
build: tests/FSharp.Control.AsyncSeq.Tests/AsyncSeqTests.fs#L1976
The result of groupBy must be consumed with a parallel combinator such as AsyncSeq.mapAsyncParallel. Sequential consumption will deadlock because sub-sequence completion depends on other sub-sequences being consumed concurrently.
build: tests/FSharp.Control.AsyncSeq.Tests/AsyncSeqTests.fs#L1967
The result of groupBy must be consumed with a parallel combinator such as AsyncSeq.mapAsyncParallel. Sequential consumption will deadlock because sub-sequence completion depends on other sub-sequences being consumed concurrently.
build: src/FSharp.Control.AsyncSeq/AsyncSeq.fs#L2175
The result of groupByAsync must be consumed with a parallel combinator such as AsyncSeq.mapAsyncParallel. Sequential consumption will deadlock because sub-sequence completion depends on other sub-sequences being consumed concurrently.
build: src/FSharp.Control.AsyncSeq/AsyncSeq.fs#L2175
The result of groupByAsync must be consumed with a parallel combinator such as AsyncSeq.mapAsyncParallel. Sequential consumption will deadlock because sub-sequence completion depends on other sub-sequences being consumed concurrently.