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.
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
[dcl.fct.def.delete] p1 Improve the phrase for "implicitly defined as deleted" #6378
Comments
You're right that his makes deleted definition and deleted function less redundant, but is this really a necessary change? What does this improve? Is the current wording problematic in some way? |
Yeah, I don't see a problem with the current wording. It doesn't really matter whether a given function is explicitly declared as defaulted and implicitly deleted, or explicitly declared as deleted, or implicitly declared and deleted, all of those are covered by [dcl.fct.def.delete] and are all deleted functions. If we need to distinguish between those cases elsewhere, we can do so. But for the purposes of defining the term "deleted function" it doesn't matter. |
How do you interpret the phrase implicitly defined as deleted, this term is not defined in the current wording. |
One that is defined as deleted without you actually saying |
This is a function with a deleted definition, indeed, a deleted function
This is the implicitly declared function that is defined as deleted, which is defined in clauses [class]. For the phrase a function that is implicitly defined as deleted, if there is no specific definition, it should refer to
The first one is partially covered by
as per [dcl.fct.def.delete] p1. It is an improvement if we define the deleted function as:
|
[dcl.fct.def.delete] p1 says:
Since in clauses [class], we say
This includes explicitly-defaulted functions and implicitly-declared functions. A deleted definition function for the explicitly-defaulted function is defined as:
So, it is an improvement to define the deleted function of the implicitly-declared function as the following:
The text was updated successfully, but these errors were encountered: