Re: [Spirit Development] Bug in today's boost_trunk -- ambiguous operator >

Hartmut Kaiser schrieb:
>> On 12/27/2010 10:24 PM, Hartmut Kaiser wrote:
[snip]
>>>> Is a preliminary revert an option? If we reverted [67342] and
>>>> [67352], it would work again?
>>>
>>> I don't think this is necessary. The changes suggested (moving at
>>> least the two fusion traits detail::enable_equality and
>>> detail::enable_comparison) into a public place (i.e. fusion::traits)
>>> and adding SFINAE enabling template parameters should do the trick for
>> now:
>>
>> <snip>
>>
>> I see this has still not be done. Are we planning on letting this bug ship
>> in 1.46?
> 
> I very much would like to have it in as soon as possible (cc'ing Christopher
> again).

I am fine with SFINAE'izing fusion::detail::enable_equality and
fusion::detail::enable_comparison . I don't think we should make those
traits public, though. I rather agree with Joel here - in the long term
we should move all those possible collidees (fusion::begin, fusion::end,
any operator in namespace fusion) in adl barriers.

Just my 2 cents ;)

-Christopher


------------------------------------------------------------------------------
Protect Your Site and Customers from Malware Attacks
Learn about various malware tactics and how to avoid them. Understand 
malware threats, the impact they can have on your business, and how you 
can protect your company and customers by using code signing.
http://p.sf.net/sfu/oracle-sfdevnl