Starting with MSVC 2017 we've been spamming the logs with this:
Unknown compiler version - please run the configure tests and report the results
which comes from boost (autoboost). However, this warning is unhelpful because autoboost does not contain boost's "configure tests".
We could raise the threshold version number (1913 to be current, or higher) but that would defer to problem. Better to follow gcc.hpp and clang.hpp which do not emit warnings for untested compiler versions. When we do hit a compiler error, we'll know.
Starting with MSVC 2017 we've been spamming the logs with this:
which comes from boost (autoboost). However, this warning is unhelpful because autoboost does not contain boost's "configure tests".
We could raise the threshold version number (1913 to be current, or higher) but that would defer to problem. Better to follow
gcc.hpp
andclang.hpp
which do not emit warnings for untested compiler versions. When we do hit a compiler error, we'll know.