Matthew Lugg 8907dc8a4f Zcu: use shortest reference trace
The logic for computing reference traces was unintentionally finding the
*longest* possible trace (approximately). I think I already tried to fix
this before, but misunderstood how my own code works. Here, we fix it
properly: by slightly reworking the logic to use one ArrayHashMap for
both the result and the traversal queue, we trivially get a proper
breadth-first traversal so that we can find the shortest possible
reference trace for every referenced unit.
2025-10-29 05:34:19 +00:00
..
2025-10-02 17:44:52 -04:00
2025-10-27 07:35:38 -07:00
2025-10-02 17:44:52 -04:00
2025-07-07 22:43:51 -07:00
2025-08-29 17:14:26 -07:00
2025-08-29 17:14:26 -07:00
2025-10-27 11:19:51 +01:00
2025-10-16 19:36:11 +01:00
2025-10-29 05:34:19 +00:00