Boost C++ Libraries: Ticket #10882: error C2668: 'boost::swap' : ambiguous call to overloaded function (MSVC)

attachment set

Thu, 18 Dec 2014 11:27:45 GMT

attachment → boost_variant_bug.cpp

attachment set

Thu, 18 Dec 2014 11:29:32 GMT

attachment → compiler_output

attachment set

Thu, 18 Dec 2014 11:30:32 GMT

attachment → compiler_version

Thu, 18 Dec 2014 13:15:38 GMT

Possibly related to: https://svn.boost.org/trac/boost/ticket/2839

owner, status, milestone changed

Antony Polukhin — Fri, 26 Dec 2014 11:12:27 GMT

owner changed from ebf to Antony Polukhin
status new → assigned
milestone To Be Determined → Boost 1.58.0

Antony Polukhin — Fri, 26 Dec 2014 13:50:18 GMT

Fixed in develop branch. tests added in this commit. Will be merged to the master branch soon.

Tue, 13 Jan 2015 12:18:40 GMT

Since which Boost version this issue is present? At least 1.56, but what about earlier versions (like 1.55)?

And does this ambiguous call resolution cause a risk on other compilers (like gcc)? Does it work by luck on gcc? Is this luck stable? Or is there a risk that under some more complicated scenario the issue could happen on gcc too (without the fix)?

Antony Polukhin — Tue, 13 Jan 2015 12:42:42 GMT

Replying to Thomas Riccardi <riccardi@…>:

Since which Boost version this issue is present? At least 1.56, but what about earlier versions (like 1.55)?

Looks like this issue exists from the very beginning of the Varinat library.

And does this ambiguous call resolution cause a risk on other compilers (like gcc)?

Yes

Does it work by luck on gcc? Is this luck stable? Or is there a risk that under some more complicated scenario the issue could happen on gcc too (without the fix)?

Issue happen if a class located in boost:: namespace is being swapped and boost/swap.hpp is included. Anyway, it's a compile-time error, so you'll definitely know if you are hit by this issue.

attachment set

Thu, 22 Jan 2015 16:18:55 GMT

attachment → boost-1.57.0-fix-boost-variant-ambiguous-call-to-swap-boost-trac-10882.patch

fix backported on boost 1.57.0

attachment set

Thu, 22 Jan 2015 16:19:18 GMT

attachment → boost-1.55.0-fix-boost-variant-ambiguous-call-to-swap-boost-trac-10882.patch

fix backported on boost 1.55.0

Thu, 22 Jan 2015 16:20:35 GMT

Replying to apolukhin:

Replying to Thomas Riccardi <riccardi@…>:

Since which Boost version this issue is present? At least 1.56, but what about earlier versions (like 1.55)?

Looks like this issue exists from the very beginning of the Varinat library.

And does this ambiguous call resolution cause a risk on other compilers (like gcc)?

Yes

Does it work by luck on gcc? Is this luck stable? Or is there a risk that under some more complicated scenario the issue could happen on gcc too (without the fix)?

Issue happen if a class located in boost:: namespace is being swapped and boost/swap.hpp is included. Anyway, it's a compile-time error, so you'll definitely know if you are hit by this issue.

Thank you for all your precise answers.

I added to this ticket 2 patches that backport the fix for this issue on boost 1.55.0 and 1.57.0.

status changed; resolution set

Antony Polukhin — Mon, 09 Mar 2015 12:04:09 GMT

status assigned → closed
resolution → fixed