• Home
  • Features
  • Pricing
  • Docs
  • Announcements
  • Sign In

steve-downey / expected / 29211257543
97%

Build:
DEFAULT BRANCH: main
Ran 12 Jul 2026 10:21PM UTC
Jobs 1
Files 3
Run time 1min
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst

12 Jul 2026 10:17PM UTC coverage: 97.013%. Remained the same
29211257543

push

github

web-flow
D4280R0: Expected Over References — paper and wording (#65)

The D4280R0 *Expected Over References* paper and its `[expected]`
wording, split out from my fork's `main` (previously tangled into the
lint PR #63). Touches only `papers/` and `docs/`.

### Paper
- Rewrite of *Expected Over References* on the P2988 abstract /
before-after / decision-log outline, plus a correction so the structure
matches the code: **one** value-reference specialization `expected<T&,
E>` (not six), with reference *errors* admitted by relaxing the `E`
constraint rather than by new specializations.
- Render the `T&, E` synopsis in Standard house style; track
`.clang-format` (`SpaceAfterTemplateKeyword: false`).

### Wording (`[expected]`)
Change-marked against a checked-in draft-standard baseline:
- `expected-base.tex` — pristine `[expected]` extracted from the working
draft (the diff baseline; do not edit).
- `expected-new.tex` — the editable copy; proposed changes as
`\added`/`\removed`/`\changed` marks, so a diff vs the baseline is
exactly the wording delta.
- `strip-wording.py` (`make strip-wording`) — strips the change markup
to produce clean text for a working-draft PR.

Wording content:
- New `[expected.ref]` subclause: `expected<T&, E>` synopsis and full
member descriptions (rebind-on-assign, temporary-binding overloads
deleted via `reference_constructs_from_temporary`, shallow-const
observers, no-steal converting construction, `value_or` by value,
uniform monadic ops passing `T&`).
- New `[expected.un.ref]` subclause: `unexpected<E&>` (pointer-backed),
and a carve-out letting a reference `E` be a valid `unexpected`
argument.
- Relax the `E`-Destructible constraint for reference errors in
`[expected.object.general]` / `[expected.void.general]`.
- Store the error as `unexpected<E>` (not a bare union member `E`) in
the primary, void, and ref specs, since `E&` can't be a union member;
make the `swap` `noexcept` specs precise for reference `E`.

Each wording commit records... (continued)

682 of 703 relevant lines covered (97.01%)

25.99 hits per line

Jobs
ID Job ID Ran Files Coverage
1 29211257543.1 12 Jul 2026 10:21PM UTC 3
97.01
GitHub Action Run
Source Files on build 29211257543
  • Tree
  • List 3
  • Changed 0
  • Source Changed 0
  • Coverage Changed 0
Coverage ∆ File Lines Relevant Covered Missed Hits/Line
  • Back to Repo
  • Github Actions Build #29211257543
  • 2d7b0104 on github
  • Prev Build on main (#29205643587)
  • Next Build on main (#29261245149)
  • Delete
STATUS · Troubleshooting · Open an Issue · Sales · Support · CAREERS · ENTERPRISE · START FREE · SCHEDULE DEMO
ANNOUNCEMENTS · TWITTER · TOS & SLA · Supported CI Services · What's a CI service? · Automated Testing

© 2026 Coveralls, Inc