Fix assignment operator in Optional #720
Merged
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.
Issue #, if available:
There are multiple issues with Optional's assignment operators and related tests:
template <typename U = T> Optional &operator=(U &&u)
is too greedy, so it's used whenever argument type differs from other assignment operators types:template <typename U = T> Optional<T> &operator=(const Optional<U> &other)
andtemplate <typename U = T> Optional<T> &operator=(Optional<U> &&other)
useother
's private membersSpecializations of a template class are completely unrelated, so they can't access each other's private members.
Tests for assignment operators for Optional class check constructors instead.
Tests use the following expressions to check assignment operators:
But constructor is used here.
The issues can be found in the first commit's CI in this PR. For example, the following code from the tests
produces these errors:
Description of changes:
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.