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

[basic.fundamental] boolean note nitpick #2483

Closed
jfbastien opened this issue Nov 16, 2018 · 2 comments
Closed

[basic.fundamental] boolean note nitpick #2483

jfbastien opened this issue Nov 16, 2018 · 2 comments

Comments

@jfbastien
Copy link
Contributor

Booleans can behave as neither true nor false, but can also behave as both true and false.
Suggested wording here: #2438 (comment)
@jfbastien jfbastien mentioned this issue Nov 16, 2018
Merged
@jensmaurer jensmaurer changed the title boolean note nitpick [basic.fundamental] boolean note nitpick Nov 16, 2018
@jensmaurer
Copy link
Member

The suggestion is to add "or might cause it to behave as if it is both \tcode{true} and \tcode{false}" to the corresponding footnote.

Opinion: I don't think attempting to inject more precision in a non-normative comment on possible results of undefined behavior is worthwhile. Actually, removing that footnote would be fine, given that the Undefined Behavior dragon is already out of the box here.

@jensmaurer jensmaurer added the decision-required A decision of the editorial group (or the Project Editor) is required. label Nov 16, 2018
@jfbastien
Copy link
Contributor Author

The Undefined Behavior Dragon might or might not be out of the box. It's up to the Dragon to decide whether it'll come out of the box, and whether you'll be allowed to observe it come out of the box.

Agreed we can just remove the note.

jfbastien added a commit to jfbastien/draft that referenced this issue Nov 29, 2018
@jfbastien
undefined boolean note clarification
2c21904 
Addresses cplusplus#2483.
@jfbastien jfbastien mentioned this issue Nov 29, 2018
Merged
@jensmaurer jensmaurer removed the decision-required A decision of the editorial group (or the Project Editor) is required. label Dec 7, 2018
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
No milestone
Development

No branches or pull requests
2 participants
@jfbastien @jensmaurer