Issues list for P2300
active 2023-12-05 → 2026-04-22 (UTC)
Activity over time
Daily event counts in the loaded window
Line chart, 870 days from 2023-12-05 to 2026-04-22. Pushes: 231 total, peak 16 in a day. Pull requests: 134 total, peak 11 in a day. Issues: 364 total, peak 79 in a day. Comments: 520 total, peak 94 in a day. Stars: 32 total, peak 2 in a day.
- Pushes
- Pull requests
- Issues
- Comments
- Stars
Stars, PRs, issues and forks are under-captured in the later part of this window. GH Archive progressively stopped capturing non-push events during 2026 — −95% or worse by the end of the window. Every series here except Pushes fades for that reason, so a decline above reflects the archive, not this repository. Pushes stay reliable throughout, so read them, and the contributor counts derived from them, as the real signal. Data health has the measurements.
Top contributors
Pushes, PRs, issues, reviews and comments — stars and forks excluded, so this is contribution rather than popularity
| Contributor | Contributions | Pushes | PRs | Comments |
|---|---|---|---|---|
| ericniebler | 784 | 149 | 127 | 234 |
| lewissbaker | 301 | 0 | 4 | 172 |
| github-actions[bot] | 82 | 82 | 0 | 0 |
| inbal2l | 31 | 0 | 0 | 30 |
| jwakely | 30 | 0 | 0 | 20 |
| JeffGarland | 13 | 0 | 0 | 5 |
| jiixyj | 11 | 0 | 0 | 7 |
| mhoemmen | 11 | 0 | 0 | 6 |
| BenFrantzDale | 9 | 0 | 0 | 6 |
| dietmarkuehl | 8 | 0 | 0 | 8 |
| LeeHowes | 6 | 0 | 0 | 6 |
| frederick-vs-ja | 4 | 0 | 0 | 2 |
| tomaszkam | 3 | 0 | 0 | 2 |
| maikel | 3 | 0 | 0 | 1 |
| aaron-michaux | 3 | 0 | 0 | 2 |
| lucteo | 3 | 0 | 0 | 3 |
| brycelelbach | 2 | 0 | 2 | 0 |
| atomgalaxy | 2 | 0 | 0 | 2 |
| msimberg | 2 | 0 | 0 | 2 |
| GorNishanov | 1 | 0 | 0 | 1 |
Recent activity
Latest issues, pull requests and releases
- Issue#358ericniebler2026-04-22 17:14`with_awaitable_senders` should use `affine` in its `await_transform`
- Issue#357ericniebler2026-04-13 00:58`COMMON-DOMAIN` should test for convertibility to `default_domain`
- Issue#352lewissbaker2025-12-14 22:36get_allocator(env) should have blanket wording that limits use of the allocator
- Issue comment#343lewissbaker2025-11-25 01:42potential dangling reference returned from `transform_sender`
- Issue#349ericniebler2025-11-16 01:26remove test for `get_env` `noexcept`-ness from `inline_scheduler`
- Issue#351ericniebler2025-11-16 01:22`run_loop` should not have a `set_error` completion signature
- Issue#351ericniebler2025-11-16 01:22`run_loop` should not have a `set_error` completion signature
- Issue#351ericniebler2025-11-16 01:22`run_loop` should not have a `set_error` completion signature
- Issue#46elbeno2025-11-09 04:21Providing environment information to algorithms that eagerly `connect` senders
- Issue#348ericniebler2025-11-04 21:51incomplete edit in [exec.when.all] p5
- Issue#346ericniebler2025-10-16 18:41`let_value(sndr, fn)` and `let_error` and `let_stopped` should specify its attributes
- Issue#346ericniebler2025-10-16 18:41`let_value(sndr, fn)` and `let_error` and `let_stopped` should specify its attributes
- Issue#346ericniebler2025-10-16 18:41`let_value(sndr, fn)` and `let_error` and `let_stopped` should specify its attributes
- Issue#346ericniebler2025-10-16 18:40`let_value(sndr, fn)` and `let_error` and `let_stopped` should specify its attributes
- Issue comment#97ericniebler2025-10-16 18:30`get_completion_scheduler` is not a forwarding sender query?
- Issue comment#342lewissbaker2025-07-04 05:18can a sender's `connect` member fn be private if it befriends `execution::connect_t`?
- Issue comment#247inbal2l2025-06-30 10:36Add ability to know when computing completion-signatures whether the call to connect() will throw
- Issue comment#247RobertLeahy2025-06-30 10:32Add ability to know when computing completion-signatures whether the call to connect() will throw
- Issue#340ericniebler2025-06-25 16:40`on(sch,sndr)` and `starts_on(sch,sndr)` should not transform the senders they returns
- Issue#340ericniebler2025-06-22 23:28`on` algorithm is using the wrong domain to find customizations
- Issue#339ericniebler2025-06-18 23:35should we permit `get_completion_signatures<Sndr,Env>()` to return a subset of `get_completion_signatures<Sndr>()`
- Issue#338ericniebler2025-05-31 23:51`scheduler` concept is missing a requirement regarding domains
- Issue comment#47nylonhat2025-05-22 09:00Rethink split as a non-allocating algorithm
- Issue#331ericniebler2025-05-19 22:51late domain-based dispatching of `schedule_from` and `continues_on` are flipped
- Issue#337ericniebler2025-05-19 22:50troubles with the customizations of `continues_on` and `schedule_from`
Totals cover only the window loaded into ClickHouse and count events, not GitHub's lifetime totals — 32 stars here means stars gained during the window, not the repo's star count.