Open fsandhei opened 1 year ago
Changed the base branch to develop
.
I'm sorry if I'm making it a bit difficult here; I forked the repository and rebased feature/optional
to develop
and created this PR against nlohmann:feature/develop
but I noticed that included 590 commits (which makes sense) but it cluttered the actual change here, so I instead changed it towards nlohmann:develop
.
I am also interested in having std::optional
support landing in future versions of this library.
I see there was a lot of discussion on how to properly support and convert c++ optional fields vs json nullable fields.
Is there a final decision on the matter? How can we revive this PR and push forward support of std::optional
fields?
@nlohmann
See that clang-tidy is failing on some checks. Apparently this is on develop, too. I see that it is related to a supposed new check from clang-tidy v19: https://clang.llvm.org/extra/clang-tidy/checks/modernize/use-designated-initializers.html.
See that clang-tidy is failing on some checks. Apparently this is on develop, too. I see that it is related to a supposed new check from clang-tidy v19: clang.llvm.org/extra/clang-tidy/checks/modernize/use-designated-initializers.html.
I'm on it. May take some more time.
has this PR stalled again?
I'm currently blocked by https://github.com/nlohmann/json/pull/4311.
Rebasing
feature/optional
in attempt to revive this PR, referring to https://github.com/nlohmann/json/pull/2117.Sorry for long time between responses.
I may have been going forward with this the "wrong" way, so I apologize in advance.
Please let me know if this should be handled differently.
TODO
There is one test that is failing: Conversions from a default initialized
nlohmann::json
tostd::optional<T>
seems to fail. In the test case below, the last assertion fails with an exception. This is tested on Arch Linux with GCC 13.1.1.I was not able to figure out how to fix this so I need some assistance here.