We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
operation_state
The current defn of the operation_state concept is:
template<class O> concept operation_state = derived_from<typename O::operation_state_concept, operation_state_t> && is_object_v<O> && requires (O& o) { { start(o) } noexcept; };
i think the is_object_v<O> constraint is not needed because the derived_from constraint has already established that O is a class type.
is_object_v<O>
derived_from
O
and start(o) is always noexcept now that start mandates the noexcept-ness of op.start().
start(o)
noexcept
start
op.start()
Change the operation_state concept to:
template<class O> concept operation_state = derived_from<typename O::operation_state_concept, operation_state_t> && requires (O& o) { start(o); };
The text was updated successfully, but these errors were encountered:
No branches or pull requests
The current defn of the
operation_state
concept is:i think the
is_object_v<O>
constraint is not needed because thederived_from
constraint has already established thatO
is a class type.and
start(o)
is alwaysnoexcept
now thatstart
mandates thenoexcept
-ness ofop.start()
.Proposed resolution:
Change the
operation_state
concept to:The text was updated successfully, but these errors were encountered: