Re: [boost] [fusion] Qualification of 'at' and 'deref' in fusion (Ticket #4755)

On 15/06/2011 00:09, Vicente Botet wrote:

If the headers qualify any symbol, the preceding is not ambiguous. Of course, the user needs to be aware that there is a potential conflict for at and deref, and should also use qualification to avoid the conflicts.

I'm missing something?

The bug is that the fusion headers do not qualify the calls.