Re: [boost] Query: ADL vs MSVC2013 support

Subject: Re: [boost] Query: ADL vs MSVC2013 support
From: Soul Studios (matt_at_[hidden])
Date: 2016-06-27 20:11:01

Any perspectives on this? Compatibility with one compiler vs support for 
ADL'd non-member functions?

On 26/06/2016 10:47 a.m., Soul Studios wrote:
> I have transplanted the advance/next/prev/distance member functions into
> ADL non-member functions in a current unreleased version of colony
> (plflib.org). My question is whether MSVC2013 support for these
> functions is more important to the boost community than them being ADL.
> There's a bug in MSVC2013 (fixed in MSVC2015, never backported to
> MSVC2013) that causes a compiler crash under certain template
> configurations - unfortunately the way that the ADL has to be
> implemented (I have tried several methods) causes this bug.
>
> The workaround would be to disable these functions in MSVC2013 only, as
> everything works fine in MSVC2010, MSVC2015, Clang 3.6-3.8 (have not
> tested earlier) and GCC 4.6-5.1 (have not tested earlier).