Skip to content

Conversation

@jbcoe
Copy link
Owner

@jbcoe jbcoe commented Feb 13, 2025

@Quuxplusone @Ukilele this may be of interest to you both.

@jbcoe jbcoe requested a review from Ukilele February 13, 2025 09:57
@jbcoe jbcoe requested a review from Twon as a code owner February 13, 2025 09:57
@codecov
Copy link

codecov bot commented Feb 13, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 99.60%. Comparing base (f5cb1b3) to head (1968bc1).

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #546   +/-   ##
=======================================
  Coverage   99.59%   99.60%           
=======================================
  Files          11       11           
  Lines         748      760   +12     
  Branches       76       76           
=======================================
+ Hits          745      757   +12     
  Misses          3        3           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

Copy link
Contributor

@Quuxplusone Quuxplusone left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Awesome. Are you proposing these for the Standard? did LEWG/LWG ask for them?

Copy link
Collaborator

@Twon Twon left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nice, I'm in favour of the added consistency these bring.

@jbcoe
Copy link
Owner Author

jbcoe commented Feb 13, 2025

These have not been asked for. They'd need adding as a NB comment, a library defect or as part of C++29.

I'd want collaborators on the standardisation effort.

@jbcoe jbcoe marked this pull request as draft February 13, 2025 11:12
@Quuxplusone
Copy link
Contributor

These have not been asked for. They'd need adding as a NB comment, a library defect or as part of C++29.

I'd want collaborators on the standardisation effort.

I'm certainly happy to help craft wording and/or coauthor (or not). I'd like to see these get in, too. Procedurally, as a design issue, this would not be a defect/LWG-issue; but as a kind of "bugfix" to new-in-C++26 material (from the original authors no less), the paper should have no trouble getting seen in LEWG in a timely fashion.

@jbcoe jbcoe marked this pull request as ready for review February 21, 2025 13:51
@Ukilele
Copy link
Collaborator

Ukilele commented Feb 25, 2025

LGTM :)

@jbcoe jbcoe marked this pull request as draft July 13, 2025 18:23
@jbcoe
Copy link
Owner Author

jbcoe commented Jul 13, 2025

@Quuxplusone @Ukilele this PR is looking for an owner who's willing or able (ideally both) to write a paper/issue for C++26.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants