Re: [Boost-users] [Type Erasure] Ambiguous call with vs 2015 community

Subject: Re: [Boost-users] [Type Erasure] Ambiguous call with vs 2015 community
From: Yuan Yao (yaoyuan0123_at_[hidden])
Date: 2015-09-01 22:43:34

在 2015/9/2 1:08, Steven Watanabe wrote:
> AMDG
>
> On 08/31/2015 04:53 AM, Yuan Yao wrote:
>> I try to use type erasure on the free function foo. However, VS 2015
>> failed to compile the following code, which is OK with GCC and CLang.
>>
>> <snip>
>> Source.cpp(7): note: could be 'std::type_index
>> boost::type_erasure::injectHasGetField<R (const
>> boost::type_erasure::_self
>> &),Base,boost::type_erasure::index_list<0>>::foo(eval_if_c<0,boost::type_erasure::detail::maybe_const_this_param<const
>> boost::type_erasure::_self
>> &,Base>,boost::type_erasure::as_param<Base,const
>> boost::type_erasure::_self &>>::type)' [found using argument-dependent
>> lookup]
> This kind of looks like a variadic
> template bug.  The condition of
> the eval_if_c is supposed to evaluate
> to true.  The whole point of this
> eval_if_c business is to prevent the
> ambiguity that you're seeing.
>
> In Christ,
> Steven Watanabe
>
> _______________________________________________
> Boost-users mailing list
> Boost-users_at_[hidden]
> http://lists.boost.org/mailman/listinfo.cgi/boost-users
You are correct. The code compiles by defining 
BOOST_NO_CXX11_VARIADIC_TEMPLATES. Thank you!