After automated rename WTF::passed function will be ambiguous wrt base::Passed.
I think the best and safest thing to do will be to namespace-qualify WTF::passed everywhere.
Summary: After automated rename WTF::passed and WTF::wrapUnique functions will be ambiguous with functions from base:: namespace (was: After automated rename WTF::passed function will be ambiguous wrt base::Passed.)
Makes sense to me too.
(I'm a little curious why WTF has traditionally decided to put all of its names into the global namespace: I suppose the other solution here is to write ::passed, but I agree that WTF::passed is the right solution)
Summary: After the "big rename" WTF::passed and base::Passed (and possibly other such pairs) will be ambiguous without namespace qualifier (was: After automated rename WTF::passed and WTF::wrapUnique functions will be ambiguous with functions from base:: namespace)
Known issues have been fixed, but let's keep this bug opened for a while, to see if we bump into other trouble-causing functions named similarily in base:: and WTF::.
Comment 1 by lukasza@chromium.org
, Dec 3 2016