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

[std] might and could: re-review for complicated cases #4340

Open
jensmaurer opened this issue Nov 11, 2020 · 4 comments
Open

[std] might and could: re-review for complicated cases #4340

jensmaurer opened this issue Nov 11, 2020 · 4 comments
Milestone
C++26

Comments

@jensmaurer
Copy link
Member

jensmaurer commented Nov 11, 2020 •
edited

[meta.rqmts] p5

that instantiation would yield a different result if performed in a context where T were a complete type

"yield a different result" -> "the validity or meaning of the instantiation depends on the completeness of T"; run by CWG / LWG.

[time.zone.info.sys]

A correct offset for the \tcode{time_zone} off daylight saving time
can be obtained by querying the \tcode{time_zone} with a \tcode{time_point}
that returns a \tcode{sys_info} where \tcode{save == 0min}.
There is no guarantee
what \tcode{time_point} (if any) returns such a \tcode{sys_info}
except that it is guaranteed not to be in the range \range{begin}{end}
(if \tcode{save != 0min} for this \tcode{sys_info}).
@jensmaurer jensmaurer added this to the C++23 milestone Nov 11, 2020
@jensmaurer jensmaurer mentioned this issue Nov 12, 2020
Merged
@tkoeppe
Copy link
Contributor

tkoeppe commented Nov 12, 2020

[basic]: "A literal type is one for which an object can possibly be created within a constant expression."

@tkoeppe
Copy link
Contributor

tkoeppe commented Nov 13, 2020

[expr]: "Historically, lvalues and rvalues were so-called because they can appear on the left- and right-hand side of an assignment" -- this is borderline incorrect; we should look for a better way to explain this historic perspective.

@tkoeppe
Copy link
Contributor

tkoeppe commented Nov 13, 2020

[expr]: "and can therefore be defined as deleted." This sounds uncomfortably ambiguous with the meaning of "and therefore you the user can define it as deleted". The previous wording wasn't quite so readily interpretable that way. Maybe extra words like "and can therefor end up as being defined as deleted".

@tkoeppe
Copy link
Contributor

tkoeppe commented Nov 13, 2020

Placeholder topic for noteworthy "good rewordings".

"These special member functions are implicitly defined as usual, and might therefore be defined as deleted." => "... as usual, which can result in them being defined as deleted."

@jensmaurer jensmaurer modified the milestones: C++23, C++26 Oct 23, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
C++26
Development

No branches or pull requests
2 participants
@tkoeppe @jensmaurer