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

Mark constructors/assignment/swap noexcept where possible #122

Closed
Lastique opened this issue Jul 26, 2020 · 1 comment
Closed

Mark constructors/assignment/swap noexcept where possible #122

Lastique opened this issue Jul 26, 2020 · 1 comment

Comments

@Lastique
Copy link
Member

Please mark functions noexcept where possible for the types provided by Boost.Interprocess. In particular, I'm interested in types shared_memory_object and mapped_region, but this is probably not limited to those.

The functions that have immediate benefit from being marked are:

  • Default constructors.
  • Move constructors and assignment.
  • Copy constructors and assignment, where possible.
  • swap.

The important effects of this markup includes:

  • More efficient implementation of standard containers and algorithms.
  • Implicitly defined constructors and operators of user's types that have Boost.Interprocess types in members or base classes become noexcept.
@igaztanaga
Copy link
Member

Many thanks for the report!

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

2 participants