<story><title>JSON for Modern C++ version 3.10.0</title><url>https://github.com/nlohmann/json/releases/tag/v3.10.0</url></story><parent_chain><item><author>esprehn</author><text>This doesn&amp;#x27;t appear to be all that &amp;quot;modern&amp;quot;: it doesn&amp;#x27;t support string_view for lookup without extra allocations, and it doesn&amp;#x27;t support unordered_map (or even use it as the default) for objects.&lt;p&gt;It seems they&amp;#x27;re targeting C++11?</text></item></parent_chain><comment><author>nlohmann</author><text>The development started in 2013 when C++11 was still modern. Since then, the term &amp;quot;modern C++&amp;quot; is, to my understanding, a synonym for &amp;quot;C++11 and later&amp;quot;. Of course, some code may look dated compared to newer C++ constructs, but the main goal is to integrate JSON into any C++ code bases without making it look odd.&lt;p&gt;The string_view lookup is nearly done, but I did not want to wait for it, because it would have delayed the release even more.&lt;p&gt;I&amp;#x27;m also working on supporting unordered_map - using it as container for objects would be easy if we would just break the existing API - the hard part is to support it with the current (probably bad designed) template API.</text></comment>
<story><title>JSON for Modern C++ version 3.10.0</title><url>https://github.com/nlohmann/json/releases/tag/v3.10.0</url></story><parent_chain><item><author>esprehn</author><text>This doesn&amp;#x27;t appear to be all that &amp;quot;modern&amp;quot;: it doesn&amp;#x27;t support string_view for lookup without extra allocations, and it doesn&amp;#x27;t support unordered_map (or even use it as the default) for objects.&lt;p&gt;It seems they&amp;#x27;re targeting C++11?</text></item></parent_chain><comment><author>MauranKilom</author><text>&amp;gt; and it doesn&amp;#x27;t support unordered_map (or even use it as the default) for objects.&lt;p&gt;std::unordered_map has massive overhead in space and time. Maybe I misunderstand your idea, but outside of &lt;i&gt;extremely&lt;/i&gt; niche use cases, std::unordered_map is basically never the right tool (unless you don&amp;#x27;t care in the slightest about performance or memory overhead).</text></comment>