This repository has been archived by the owner on Dec 8, 2021. It is now read-only.
style: cleanup use of noexcept
, explicit
and = default
#1209
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Our current rule-of-thumb is to only specify
noexcept
on hand-writtenmove constructors and assignments. So, remove two current specifications
on defaulted move operators, and one on a normal constructor. Fixes #228.
Reserve
explicit
for single-argument constructors. Some ctor-arityhas changed over time, so some
explicit
annotations were missing oroutdated.
Also rewrite any
T() {}
constructor asT() = default
.This change is