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

[defns.valid] Elaborate on cause in example and add cross-references #7366

Closed
Closed
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 4 additions & 2 deletions source/intro.tex
Original file line number Diff line number Diff line change
Expand Up @@ -665,8 +665,10 @@
met and operations on the object behave as specified for its type

\begin{example}
If an object \tcode{x} of type \tcode{std::vector<int>} is in a
valid but unspecified state, \tcode{x.empty()} can be called unconditionally,
If an object \tcode{x} of type \tcode{std::vector<int>} enters a
valid but unspecified state through say,
a move operation\iref{lib.types.movedfrom,class.copy.ctor,class.copy.assign},
\tcode{x.empty()} can be called unconditionally,
and \tcode{x.front()} can be called only if \tcode{x.empty()} returns
\tcode{false}.
\end{example}
Expand Down
Loading