-
Notifications
You must be signed in to change notification settings - Fork 2.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[VS2019] Fails to compile after commit f57227a148f19723fe3c7b601c25f1d9f48ee079 #1186
Comments
I wasn't able to repro it: https://ci.appveyor.com/project/vitaut/fmt/builds/24972186/job/56ptnunfmh77ushi Moreover, the lines don't seem to match revision Line 1312 in f57227a |
no it is in the f57227a commit HEAD is now at f57227a FMT_ENABLE_IF -> enable_if_t
i will try the latest one |
same thing HEAD is now at 67feef5 Make enable_if_t more std-like and move to fmt namespace
|
Please provide a repro example. |
fmtlib_die.cpp
cl.exe fmtlib_die.cpp /permissive- /diagnostics:caret
|
Probably related to issue #1140 and fix #1150 which I implemented.
Haven't read changes yet so might be wrong, though. |
yep changing
to
fixed compiling |
possibly because the reproduction example supplied is using the |
Probably we can. But we need to add parentheses on every use of
Not sure this is related to this issue, but AppVeyor also supports preview image of VS2019 as |
Doesn't seem so, at least not on v19.20: https://godbolt.org/z/uceqRl
MSVC builds are extremely slow, so maybe only as a single config (without Debug/Release 32/64 variations). |
VS2019 16.0.28625.61
MSVC 14.21.27702
Compile Log (big)
The text was updated successfully, but these errors were encountered: