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

steve-downey / free_value_or / 34076657849
98%

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

push

github

steve-downey
Correct the rvalue argument: the split is ownership, not uniformity

The previous revision argued that moving payloads out of rvalue nullables
"does not generalize", treating the divergence between optional/expected and
the pointers as an inconsistency decided by a property the caller has no
reason to know. That was wrong, and it was the wrong shape of argument.

The divergence is ownership, and it is principled. optional and expected
contain their value, so an expiring one has an expiring payload, and
operator* is ref-qualified to say so. A pointer contains nothing: an rvalue
shared_ptr, unique_ptr or T* is an expiring handle to a referent that
ordinarily outlives it, so T& is the truthful answer. optional<T&> settles
which property is doing the work -- it is an optional, and it dereferences
to T&, because it does not own its referent. Verified against the Beman
optional: deref of an rvalue optional<int&> is int&, grouping it with the
pointers and not with optional<int>.

So the moving alternative would not misbehave. Each nullable would report
what its own value category implies about its payload, and every model would
be right. The paper now says that, and says what follows from it: the case
for the proposed rule is not correctness but cost and simplicity of
statement -- a return type that stops depending on value category,
reference_or over an rvalue optional<int> staying int& instead of becoming
const int&, and no moved-from path under the dangling analysis. It closes by
conceding that is not decisive, which is why the question is open at all.

The open-questions entry and the test file's comment carried the same wrong
framing and are corrected with it.

1090 of 1126 relevant lines covered (96.8%)

17812.97 hits per line

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