On 10/04/2017 03:24, Edward Diener via Boost wrote:
Please, please library authors this is important. No end-user or tester of your library wants to spend extended time trying to figure out why some compile fails when the answer turns out simply to be one of inadequate C++ conformance level for a particular compiler implementation being used with a particular level of conformance.
Outcome is up for review here end of May. Are you happy with its compiler support at https://ned14.github.io/boost.outcome/prerequisites.html? To save people clicking on the link: "Outcome is a header only C++ 14 library known to work on these compilers or better: clang 3.5 (LLVM) clang 3.7 (with Microsoft Codegen) GCC 5.4 VS2015 Update 2 Xcode 7.3 *A copy of Boost is not required to use this library. You can simply drop Outcome into your project and go.* Warning: MSVC generates significant code bloat when using Outcome in large code bases. If you can use VS2017 which implements C++ 14 constexpr and has a better optimiser for modern C++, you will see tigher executables. Execution speed is not particularly different, though one would have thought the extra cache load caused by code bloat might affect some applications. In this situation, use LLVM clang targeting the MSVC ABI." Niall -- ned Productions Limited Consulting http://www.nedproductions.biz/ http://ie.linkedin.com/in/nialldouglas/