Parameter pack issue on VS2015 about range-v3 HOT 9 CLOSED

But I think VS 2015 would be a really really reasonable and awesome target for this library to run on.

Sadly not. Range-v3 requires a conforming C++11 compiler. VS 2015 doesn't make the cut. Range-v3 needs generalized SFINAE for expressions. It's not even on the VC++ roadmap, I'm afraid.

from range-v3.

That feature is definitely on the VC++ roadmap. It's in the fifth column, half way down, next to C++11 preprocessor.

from range-v3.

next to C++11 preprocessor.

Lol

from range-v3.

I'm looking at slide 3 of Herb's slide deck here. I see things that have a medium probability of making it into 2015 colored yellow. Expression SFINAE is left white. To me, it says that expression SFINAE isn't making the cut for 2015. AFAIK, Microsoft hasn't said when the feature is likely to appear.

EDIT: And to be clear, the feature needs to exist, and it needs to work reliably. There's a good chance that Microsoft doesn't get it right (or right enough) on the first try. Really, I don't see range-v3 compiling on an officially supported Microsoft compiler within the next 2 years.

from range-v3.

Thank you very much for the detailed explanation! I'm very sad to hear that, but the ball clearly seems to be in Microsofts hands. Too bad! Thank you!

from range-v3.

Their compiler architecture is ancient and thus they are struggling a lot with this feature.

from range-v3.

http://blogs.msdn.com/b/vcblog/archive/2015/04/29/c-11-14-17-features-in-vs-2015-rc.aspx

We're planning to start implementing Expression SFINAE in the compiler immediately after 2015 RTM, and we're planning to deliver it in an Update to 2015, supported for production use.  (But not necessarily 2015 Update 1.  It might take longer.)

from range-v3.

Even once they implement it, the probability that VC++'s expression SFINAE will be robust enough to handle range-v3 on their first outing is ... small. Unless they test with range-v3, that is.

from range-v3.

FWIW they do test against range-v3.
@ericniebler does range-v3 use two-phase look-up a lot? I would be more worried about this.

from range-v3.