Edition of Friday 13 November 2026

Senders and Coroutines Together

Comments on “Senders and Coroutines Together”

Claim-checked. Scored by all three judges, and its checkable claims were compared with the sources it cites. How far stories are checked

Train IT's sixth-to-eighth installment on std::execution shows how C++26 coroutines and senders combine. A std::execution::task is itself a sender, and co_await turns set_error into an exception, so a plain try/catch loop replaces a custom retry sender. A stop request destroys coroutine frames without resuming them. Tasks resume on their start scheduler by default, at the cost of a reschedule per co_await. In stdexec, a task awaiting two tasks allocates three times; a two-step pipeline allocates none. Several standards details were not independently verified.

Read the original at train-it.eu. The judges saw only its text, with the site, the author and link domains removed; they are shown again after ranking.

Why it ranked

No. 16 of 137 with a score of 0.63. The panel rated it highest on technical depth (0.96) and new information (0.94), lowest on audience breadth (0.53). Placed No. 16, No. 40 by score alone: the placement terms moved other stories past it.

AI judgeJudge 2claude-haiku-5-5
A detailed, technically deep tutorial on C++26 std::execution coroutine tasks with concrete examples. Strongly on topic for programmers, though it is a niche language-feature series part, with a mild promotional closing plug for training.
AI judgeJudge 3gpt-5.6-luna
A deeply technical, well-supported C++26 senders/coroutines guide with reproducible examples, semantics, cancellation, scheduler affinity, allocation tradeoffs, and practical design guidance. It is highly useful to advanced C++ builders, though narrower than mainstream tech.

Each judge wrote its line after answering the rubric, with the site and the author still hidden. Every answer behind this is in the table under Score.

Score

0.63total under rubric v2.3

Judges’ mean answer per question, on a scale from 0 to 1. Questions marked minus count against the score.
  • Significance0.56
  • Reader interest0.68
  • Audience breadth0.53
  • Practical relevance0.70
  • Substantiated0.79
  • Technical depth0.96
  • New information0.94
  • Counts against: Promotional0.12
  • Counts against: Overclaim0.13

Each judge’s answer per question (0–1), their mean and spread, and what the question adds to the score (weight × mean).

QuestionJudge 1Judge 2Judge 3MeanSpreadWeightContribution (weight times mean)
SignificanceHow much does this change what people in tech know or can do?0.560.400.720.560.32+0.24+0.135
Reader interestWould a well-informed senior engineer or tech founder want to read this today, and likely pass it on?0.530.600.900.680.37+0.26+0.176
Audience breadthHow many people who build technology does it concern?0.480.500.620.530.14+0.13+0.069
Practical relevanceHow useful is it to someone who builds software or tech products?0.680.600.820.700.22+0.22+0.154
SubstantiatedHow well is it backed? Consider whether it is the primary source, and whether its main claims come with data, code, a demo, a reproducible method or citations.0.760.700.920.790.22+0.05+0.040
Technical depthHow technically substantive is it?0.990.900.980.960.10+0.05+0.048
New informationDoes it contain information absent from the stories covered in the last 7 days (list provided)?0.920.900.990.940.09+0.05+0.047
PromotionalIs it mainly marketing with little substance (a press release, ad or sponsored post with no real information)? A launch post that carries real news is not promotional.0.040.250.080.120.21−0.19−0.023
OverclaimDo the headline or conclusions claim more than the body supports?0.110.200.080.130.12−0.11−0.014
Sum of contributions+0.630
Claim-check penalty0.000
Total, as published0.630

Spread is the highest minus the lowest judge answer. marks a spread above 0.40: the judges disagree, and the story is marked contested.

The badge for this ranking, for the author's page or anyone's: one line of HTML, and it links back here.

Ranked #16 on Rubric, 13 Nov 2026
<a href="https://rubric.hrih.si/editions/2026-11-13/16/"><img src="https://rubric.hrih.si/badge/2026-11-13/16.svg" alt="Ranked #16 on Rubric, 13 Nov 2026" width="245" height="28"></a>

Claim check

Claim check: 1 matches source · 2 no source given · 5 couldn’t check. Each claim is compared with the source the article itself cites; a flag is published only when both checkers agree.

  1. Couldn’t checkVersion

    C++26 adds std::execution::task as a standard coroutine task type that implements the sender interface.

    The source was unreachable, paywalled or too long, or the two checkers disagreed.

    The article says

    “the coroutine type C++26 adds as std::execution::task (covered at the end of this post). task implements the sender interface itself”

    The source says

    No passage could be compared.

    Source cited by the article: wg21.link/p3552

  2. Matches sourceCausal conclusion

    When an awaited sender completes with set_stopped(), the coroutine is never resumed; the promise's unhandled_stopped() is called instead, which for a task destroys the coroutine frame and completes the task with set_stopped().

    The cited source says the same thing.

    The article says

    “It calls unhandled_stopped() on the promise, which for a task destroys the coroutine frame and completes the task with set_stopped”

    The source says

    “The asynchronous operation is completed by first destroying the coroutine frame using st.handle.destroy() and then invoking set_stopped(std​::​move(st.rcvr”

    Source cited by the article: wg21.link/task.promise

  3. No source givenGeneralization

    What gets thrown at a co_await on set_error(e) depends on the type of e: an std::exception_ptr is rethrown, an std::error_code is thrown as std::system_error, and anything else is thrown as itself.

    The article gives no link or citation for it.

    The article says

    “An std::exception_ptr is rethrown, an std::error_code is thrown as std::system_error, and anything else is thrown as itself”

    The source says

    No source to compare with.

  4. Couldn’t checkGeneralization

    as_awaitable requires at most one value completion signature; for other senders (without the opt-in hook) it returns the sender unchanged.

    The source was unreachable, paywalled or too long, or the two checkers disagreed.

    The article says

    “as_awaitable requires at most one value completion signature”

    The source says

    No passage could be compared.

    Source cited by the article: wg21.link/exec.as.awaitable

  5. Couldn’t checkVersion

    P3570, adopted for C++26, gave senders an opt-in hook, get_await_completion_adaptor, for collapsing their own completions.

    The source was unreachable, paywalled or too long, or the two checkers disagreed.

    The article says

    “P3570, adopted for C++26, gave senders an opt-in hook for it, get_await_completion_adaptor”

    The source says

    No passage could be compared.

    Source cited by the article: wg21.link/p3570

  6. Couldn’t checkGeneralization

    std::execution::task is scheduler-affine by default: it keeps the scheduler it was started on and wraps every awaited sender in affine, which moves completion back to that scheduler with continues_on.

    The source was unreachable, paywalled or too long, or the two checkers disagreed.

    The article says

    “std::execution::task is scheduler-affine by default. When it starts, it takes the scheduler it was started on from its receiver’s environment and keeps it”

    The source says

    No passage could be compared.

    Source cited by the article: wg21.link/exec.affine

  7. Couldn’t checkDate

    P3950 by Robert Leahy was adopted in June 2026 as a Defect Report, lifting the restriction that a promise cannot have both return_void() and return_value().

    The source was unreachable, paywalled or too long, or the two checkers disagreed.

    The article says

    “P3950 by Robert Leahy, adopted in June 2026 as a Defect Report, lifts that restriction”

    The source says

    No passage could be compared.

    Source cited by the article: wg21.link/p3950

  8. No source givenNumber

    A task that awaits two other tasks allocates three times in stdexec, once per coroutine call, while a two-step then pipeline run with sync_wait allocates nothing.

    The article gives no link or citation for it.

    The article says

    “a sender pipeline of two then steps run with sync_wait allocates nothing, while a task that awaits two other tasks allocates three times in stdexec, once per coroutine call”

    The source says

    No source to compare with.

Also covered by

No other coverage was clustered with this story.

Elsewhere

Elsewhere: HN 1 pts, not on front page

Discussion on Hacker News

Recorded for context only, checked 15 Nov 2026, 20:42 UTC. It played no part in the ranking.

Panel for this edition

Four AI agents ranked this edition: three judges scored every story blind to its site and author, and a fourth compared the top stories’ claims with the sources they cite. Summaries are written by AI.

Model versions are pinned for every edition. How ranking works describes rubric v2.3.

Comments

Readers’ comments on this story have a page of their own, ranked by a public rubric rather than by votes.

Comments on “Senders and Coroutines Together”

More on Rubric

From the last 7 editions, chosen by shared topic, score and date.