ValueTaskSeq for ValueOption and ValueTask #466

Activity

1. github-actions

   added

   enhancementNew feature or requestNew feature or request

   needs triage

   on Sep 11, 2026
2. github-actions commented on Oct 10, 2026

   

   github-actionsbot

   on Oct 10, 2026 – with GitHub Actions

   Contributor

   More actions

   🤖 This is an automated response from Repo Assist.

   Thanks for the suggestion, @xperiandri! To help scope this, could you clarify which of these you mean?

   1. Value-returning combinators on the existing TaskSeq<'T>, e.g. tryHeadV/tryFindV returning voption, or ...ValueAsync variants taking 'T -> ValueTask<'U>. Note chooseV/chooseVAsync already exist for voption choosers.
   2. A separate ValueTaskSeq type or builder whose enumerator is built on ValueTask. Note IAsyncEnumerable<'T> already uses ValueTask<bool> for MoveNextAsync.

   A concrete example of the call site you'd like to write, and the allocation or API ergonomics problem it solves, would help us judge feasibility. Option 1 looks like a reasonable incremental addition; option 2 would be a much larger design change.

   Generated by 🌈 Repo Assist, see workflow run. Learn more.
   _{Comment /repo-assist to run again}

   _{Add this agentic workflow to your repo}

   To install this agentic workflow, run

   gh aw add githubnext/agentics/workflows/repo-assist.md@b4e175bab6674279e0fe158f7dc877b77bc9d92f