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.

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

[vector.bool] Excise use of undefined term 'conversion operator' #1018

Merged
merged 1 commit into from Nov 13, 2016

Conversation

jensmaurer
Copy link
Member

Fixes #444.

@@ -1289,7 +1289,7 @@
\ref{istream::sentry},
\ref{ostream::sentry},
\ref{iostate.flags}
\change Specify use of explicit in existing boolean conversion operators
\change Specify use of explicit in existing boolean conversion functions
Copy link
Contributor

Choose a reason for hiding this comment

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

Should "explicit" appear in code font, since it's actually a keyword?

Copy link
Member Author

Choose a reason for hiding this comment

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

Yes, but I shouldn't make that change here, which deals with "conversion operator" vs. "conversion function".

I've created #1019 to deal with the "explicit" code font issue.

Copy link
Contributor

Choose a reason for hiding this comment

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

OK, sure, but I would have had no problem with a minor drive-by fix like that if this is a single, isolated problem. You can stick it into a separate commit in the same pull request, and I could retain the separate commits (i.e. not squash them), so we still get nicely atomic commits.

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.

None yet

2 participants