The unordered map container currently underperforms by a factor of ~2× on insert/lookup workloads. A…
The unordered map container currently underperforms by a factor of ~2× on insert/lookup workloads. A…: a task in LegoFlow-SWE (Harbor dataset). A secondary, but related, API problem exists: the function unordered map size returns int instead of size t . For maps that can hold a very large number…
The task
A secondary, but related, API problem exists: the function `unordered_map_size` returns `int` instead of `size_t`. For maps that can hold a very large number of elements, returning `int` risks overflow and is inconsistent with standard memory‑size conventions. The correct signature is:
Part of Lego-X/LegoFlow-SWE.