mul(a,b,c) with visual studio 2017 release candidate about linalg HOT 5 CLOSED

As a quick workaround, you can simply delete the

-> decltype(mul(a, mul(r...)))

clause, which isn't necessary in C++14.

I might go ahead and update the whole library in a bit to rely on C++14 features. Microsoft is claiming that they should have FULL C++98/11/14 compatibility (even two phase lookup!) for the actual release of Visual Studio 2017. GCC and Clang have had it for a couple of years. It's probably time.

from linalg.

Yes, tested and it works. Just removing the specification of the return leads to successful compilation for code with both 2015 and 2017. Given the compiler deduces the type anyways, this seems to be an acceptable solution rather than just a 'workaround'. Any reason to not simply close the issue?

from linalg.

It's a breaking change for anyone still compiling with a C++11 compiler, which means I should probably bump the major version number, and if I'm going to declare linalg v3.0 and a dependency on C++14, I kinda want to go ahead and update a number of things.

from linalg.

One suggestion. You might want to try variadic templates. Worked great on some test code I wrote recently. If you are interested, I can upload a few test cases I wrote on this.

from linalg.

Looks like somewhere along the way I added an explicit workaround.

from linalg.