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

steve-downey / free_value_or / 34075925961
98%

Build:
DEFAULT BRANCH: main
Ran 07 Sep 2026 02:24AM 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 02:19AM UTC coverage: 96.803%. Remained the same
34075925961

push

github

steve-downey
Argue the rvalue question from non-uniformity

The Design section listed the costs of moving payloads out of rvalue
nullables -- a return type that depends on the value category, a moved-from
path under the dangling analysis -- and led with neither of the two, because
neither is the real reason. The reason is that moving does not generalize
across the concept.

optional and expected ref-qualify operator*, so dereferencing an rvalue of
one yields T&&. shared_ptr, unique_ptr and raw pointers return T& whatever
their own value category, and nothing these functions do can change that.
Moving would therefore reach optional and expected and leave every pointer
model copying: one rule for half the concept and another for the other half,
decided by a property of each type the caller has no reason to know. For a
proposal whose claim is that one set of semantics covers every nullable,
that is the argument. The other two costs are secondary and now read as
secondary.

The open-questions entry says the same thing in one sentence, so the room
sees the real cost without opening the Design chapter.

Implementation Experience picks up the rvalue tests: the matrix line now
says the rvalue cases are copy-counted on the engaged path, and the
harness-validation paragraph records that the mutation was run against the
library as well as against the diagnostics -- reference_or fails to compile,
four copy counts fail with those assertions removed, and the smart pointer
cases keep passing, which is the non-uniformity itself showing up as test
output. Count corrected to 117 test cases, and to nine negative-compilation
cases over eight translation units; the previous revision said nine
translation units.

1090 of 1126 relevant lines covered (96.8%)

17812.97 hits per line

Jobs
ID Job ID Ran Files Coverage
1 34075925961.1 07 Sep 2026 02:24AM UTC 7
96.8
GitHub Action Run
Source Files on build 34075925961
  • 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 #34075925961
  • 0506f91b on github
  • Prev Build on main (#34074932888)
  • Next Build on main (#34076657849)
  • 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