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

steve-downey / free_value_or / 34070152215
98%

Build:
DEFAULT BRANCH: main
Ran 07 Sep 2026 12:40AM UTC
Jobs 1
Files 7
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

07 Sep 2026 12:32AM UTC coverage: 96.803%. Remained the same
34070152215

push

github

steve-downey
Cut the LEWG asks from nine to two, and name the concept

The paper carried eight enumerated open questions plus a ninth stranded in
the prose of "Why free functions". LEWG answers few questions well and none
quickly, so most of these were spending the room's attention on things we
can decide ourselves.

Two are genuine forks and stay. reference_or silently degrades to a prvalue
when the payload and the alternative are unrelated, so reference_or over an
optional<int> and a long& yields a long: the caller who reached for it to
avoid a copy gets one, and writes through the result do not reach the
original. And an rvalue nullable does not move its payload, because
iter_reference_t is computed from an lvalue, so value_or(move(o), u) copies
where move(o).value_or(u) moves; or_invoke and or_construct too. Both items
now state the current behavior, so the room can answer without reading the
Design chapter first.

nullable becomes a named, public concept rather than an exposition-only
constraint. The argument is unchanged and the concession kept -- a public
name is forever, and boolean-testable is exposition-only for that reason --
but boolean-testable is plumbing for other concepts, where nullable is what
users want to write down, and a constraint nobody can name is one every
codebase re-derives differently. The wording gains the semantic requirements
a public name has to carry. LEWG can take the name back; that costs only the
spelling.

No naming poll. The paper proposes value_or, reference_or, or_invoke and
or_construct and leaves it there.

Decided in prose instead of asked: the dangling guards are Mandates, the
concept stays minimal so function pointers are rejected downstream, the
names do not inhibit ADL, or_construct's reference Ret is described rather
than polled, and the header is <optional>.

1090 of 1126 relevant lines covered (96.8%)

17812.94 hits per line

Jobs
ID Job ID Ran Files Coverage
1 34070152215.1 07 Sep 2026 12:40AM UTC 7
96.8
GitHub Action Run
Source Files on build 34070152215
  • Tree
  • List 7
  • Changed 0
  • Source Changed 0
  • Coverage Changed 0
Coverage ∆ File Lines Relevant Covered Missed Hits/Line
  • Back to Repo
  • Github Actions Build #34070152215
  • ec37d80b on github
  • Prev Build on main (#34069335376)
  • Next Build on main (#34074932888)
  • Delete
STATUS · Troubleshooting · Open an Issue · Sales · Support · CAREERS · ENTERPRISE · START FREE TRIAL · SCHEDULE DEMO
ANNOUNCEMENTS · TWITTER · TOS & SLA · Supported CI Services · What's a CI service? · Automated Testing

© 2026 Coveralls, Inc