Greg Marr
Greg Marr
@nlohmann It seems like we get an issue report for this about every two months or so. Seems like we should add something to the top of the issue template...
@nlohmann Did we add anything to the template?
@nlohmann It seems like we get an issue report for this about every two months or so. Seems like we should add something to the top of the issue template...
@stevenwdv You didn't check the "The bug also occurs if the latest version from the [develop](https://github.com/nlohmann/json/tree/develop) branch is used." box. Does that mean it doesn't happen anymore, or did you...
The 3.11.3 version is almost two years old, should at least confirm in 3.12.0 which is from April.
The forward declarations aren't required for the macro definition, they're required where the things are used. ~I think the issue is that it's using the detail namespace. I don't think...
> its still failing a few tests is that concerning?? Yes, one says you need to include `` in `macro_scope.hxx`. The fix for the other two is here: https://github.com/nlohmann/json/blob/af524ab666359f09a16bca1a41543a9a3a941251/tests/src/unit-unicode3.cpp#L23-L25 The...
Ugh, `JSON_THROW` is undefined by `macro_unscope.hpp`. @nlohmann Thoughts on letting that stay defined? Otherwise I guess there would need to be a helper function to do the actual `JSON_THROW`.
> ``` > template > inline void throw_enum_error(const BasicJsonType& j, const char* enum_type) > { > JSON_THROW(::nlohmann::detail::type_error::create( > 302, std::string("invalid value for ") + enum_type + ": " + j.dump(),...
@nlohmann Looks like the workflows here are awaiting approval. Not sure why since they ran before.