Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

P2895 noncopyable and nonmoveable utility classes #1534

Closed
brycelelbach opened this issue May 24, 2023 · 2 comments
Closed

P2895 noncopyable and nonmoveable utility classes #1534

brycelelbach opened this issue May 24, 2023 · 2 comments
Labels
B3 - addition Bucket 3 as described by P0592: material that is not mentioned in P0592 C++26 Targeted at C++26 IS Ship vehicle: IS LEWG Library Evolution ready-for-library-evolution-mailing-list-review This paper needs to be discussed on the Library Evolution mailing list scheduled-for-library-evolution This paper has been scheduled for one of the groups: LEWG, LEWG Incubator, or a Mailing List review size - small paper size estimate

Comments

@brycelelbach
Copy link

brycelelbach commented May 24, 2023 •
edited

P2895R0 noncopyable and nonmoveable utility classes (Sebastian Theophil, Jonathan Müller)
@brycelelbach brycelelbach added LEWG Library Evolution IS Ship vehicle: IS B3 - addition Bucket 3 as described by P0592: material that is not mentioned in P0592 C++26 Targeted at C++26 ready-for-library-evolution-mailing-list-review This paper needs to be discussed on the Library Evolution mailing list size - small paper size estimate labels May 24, 2023
@inbal2l inbal2l added the scheduled-for-library-evolution This paper has been scheduled for one of the groups: LEWG, LEWG Incubator, or a Mailing List review label Aug 30, 2023
@cor3ntin
Copy link

Review on the mailing list started

@cor3ntin
Copy link

cor3ntin commented Sep 29, 2023 •
edited by inbal2l

Mailing list outcome:

The paper was sent for a mailing list review on September 18th: https://lists.isocpp.org/lib-ext/2023/09/25769.php

The approach in the paper was not supported, and LEWG had a strong sentiment against it, for the following reasons:

  • There was a strong consensus that deleting the constructors was a more correct, equally convenient approach.
  • These classes, if used, would increase the size of some classes in the case of multiple inheritance, so they are not a replacement for existing facilities.
  • LEWG also observed that if one prefers that mechanism over deleting members, it is easy to implement them in a code base, which does not need to be the standard library.

The issue will be closed, if the authors want to pursue this further with stronger motivation (addressing the feedback given), they are of course free to do so by publishing a new revision. In this case, we will reopen the discussion in LEWGI.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
B3 - addition Bucket 3 as described by P0592: material that is not mentioned in P0592 C++26 Targeted at C++26 IS Ship vehicle: IS LEWG Library Evolution ready-for-library-evolution-mailing-list-review This paper needs to be discussed on the Library Evolution mailing list scheduled-for-library-evolution This paper has been scheduled for one of the groups: LEWG, LEWG Incubator, or a Mailing List review size - small paper size estimate
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@brycelelbach @cor3ntin @inbal2l