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

Consider adding noexcept to buffer sequence requirements #41

Open
chriskohlhoff opened this issue Sep 13, 2016 · 0 comments
Open

Consider adding noexcept to buffer sequence requirements #41

chriskohlhoff opened this issue Sep 13, 2016 · 0 comments

Comments

@chriskohlhoff
Copy link
Contributor

[buffer.reqmts.mutablebuffersequence], [buffer.reqmts.constbuffersequence], [buffer.seq.access]

We should consider:

  • Adding "Shall not exit via an exception." to the the requirements for net::buffer_sequence_begin(x) and 'net::buffer_sequence_end(x).
  • Requiring that the conversion of the iterator value type to const_buffer or mutable_buffer should not exit via exception.
  • (And perhaps place the same requirement on the iterator traversal and dereference too, although I'm not sure if this is already implied elsewhere in the standard?)
  • Adding noexcept to the buffer sequence access functions.

The current implementation in asio assumes that these never throw, and in general I think low level buffer operations should not throw.

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

No branches or pull requests

1 participant