Fix clang compilation when T is constructible from other types #64
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.
The problem was with copy/move constructors of
boost::optional<T>
, which invokedoptional_base<T>
constructors with a single argument. Sinceoptional_base
has copy/move constructors along with initializing constructors taking a single argument, the latter may be considered by the compiler for viability. While doing so, the compiler may instantiate the template constructor ofT
with an argument ofoptional_base<T>
, which in turn may fail if the constructor attempts to inspect the type of its argument (e.g. to constrain the set of acceptable types). Specifically, this happens with clang in C++03 mode, whenboost::multiprecision::number
is wrapped inboost::optional
and a copy constructor ofboost::optional
is invoked.This PR fixes the problem by destinguishing copy/move constructors of
optional_base
from initializing constructors with an additional tag argument. The PR also adds a test.