When the /permissive- flag is used (in the current preview of VS2017) there are a couple strange errors. It gets a different type than expected, but this doesn't seem to match any of the affects noted at https://blogs.msdn.microsoft.com/vcblog/2016/11/16/permissive-switch/
and in any case I wouldn't expect better conformance to break more things!
For example, test\view\const.cpp(56) gets common_pair<const int&, const int&> for the result of iter_move(begin(rng3)) when the test expects common_pair<int const&&, int const&&>. In this case, iter_move did not do its job. But look at the previous lines (53,54) where it did work!
When the /permissive- flag is used (in the current preview of VS2017) there are a couple strange errors. It gets a different type than expected, but this doesn't seem to match any of the affects noted at https://blogs.msdn.microsoft.com/vcblog/2016/11/16/permissive-switch/ and in any case I wouldn't expect better conformance to break more things!
For example, test\view\const.cpp(56) gets common_pair<const int&, const int&> for the result of iter_move(begin(rng3)) when the test expects common_pair<int const&&, int const&&>. In this case, iter_move did not do its job. But look at the previous lines (53,54) where it did work!