Repository navigation
Uniform initialization from another json object differs between gcc and clang. #985
Description
Construction behaves differently with gcc 7.2 and clang 5.
Code to reproduce:
auto j1{nlohmann::json::parse("5")};
auto j2 = nlohmann::json::parse("5");
std::cout << j1.is_array() << '\n';
std::cout << j2.is_array() << '\n';
gcc prints:
1
0
clang prints:
0
0
Both are nlohmann::json instances however j1 has an array wrapped around in gcc.
Activity
theodelrieu commentedon Feb 27, 2018
IIRC the
auto i{2}form has been fixed in C++17, before it would deduce tostd::initializer_listinstead ofint.I guess this is the same thing here. If you enable more warnings you should see Clang tell you something like "the meaning of this initialization will change in the future".
My recommendation would be to not use it at all, uniform initialization is quite borken :/
nlohmann commentedon Feb 28, 2018
I fear there is nothing we can do about this. :-/