Add GCC and MSVC settings to ensure C++ standard conformance#130
Conversation
|
Coverage report is available at: full | review summary |
…antic errors on GCC 7
…ausing -Wpedantic errors on GCC 7
Pull Request Test Coverage Report for Build ffc61b29-c678-4be2-9cce-415c1e565ae2Details
💛 - Coveralls |
|
Coverage report is available at: full | review summary |
|
Coverage report is available at: full | review summary |
|
Coverage report is available at: full | review summary |
|
Coverage report is available at: full | review summary |
|
Coverage report is available at: full | review summary |
|
I think the compilation error with MSVC 2017 is due to a bug in MSVC 2017 triggered by |
|
Coverage report is available at: full | review summary |
|
Alright, it seems that MSVC 2017 with While I would have liked to update our dependencies shortly before releasing XLNT 1.7.0, I will make an exception here (and we can also update |
This reverts commit a2b58e3.
|
Coverage report is available at: full | review summary |
m7913d
left a comment
There was a problem hiding this comment.
I'm already approving, so you can merge the PR once the failed test is fixed (by the other PR).
Updates `fmt` to 12.1.0. This also fixes an issue when using MSVC 2017 with `/permissive-`, which breaks due to issue fmtlib/fmt#4412 and has been fixed by PR fmtlib/fmt#4413, which is available since `fmt` 11.2.0. We were previously using a commit from the `master` branch from `fmt` between 11.1.2 and 11.1.3. For more details, see discussion on PR #130
|
Coverage report is available at: full | review summary |
To ensure C++ standard conformance in the future, this PR:
-Wpedanticfor GCC, and-pedantic-errorsifXLNT_ALL_WARNINGS_AS_ERRORSis set/permissive-for MSVC 2017 and newer-Weverything, which already sets-WpedanticDepends on #131 to fix compilation under MSVC 2017 (see discussion below).