Re: [boost] [Bind] TR1 and overload ambiguity.

I actually consider this to be a vital usability feature. It would be an unpleasant surprise if it's not going to make it into comforming TR1 implementations. Or did I misunderstand your earlier comment?

I don't know if it's possible to support this, and to support the named-return-type syntax as well. I also don't see anything in the TR1 text that requires this to be supported... Peter? John.