arnavsacheti / PeakRDL-BusDecoder / 28907563270

92%

push

github

perf: drive RDL parameter trace inline from DesignScanner (#64)

When parametrize=True, RdlParameterExtractor.extract() previously did
three full top_node.descendants() walks (clear caches, force re-eval,
collect arrayed nodes) on top of the DesignScanner walk. Now the
scanner installs the ParameterRef trace via a context manager and
calls reevaluate_node / record_arrayed_node per-node during its
existing walk; classify() runs after.

- New: RdlParameterExtractor.trace() context manager, reevaluate_node,
  record_arrayed_node, classify (phases extracted from extract()).
- extract() retained as a standalone wrapper for the direct test API.
- DesignState pulls results from scanner.param_extractor.classify().

Tests: 174 passed (1 skipped) — exporter fixtures byte-identical.

Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

48 of 54 new or added lines in 3 files covered. (88.89%)

1561 of 1685 relevant lines covered (92.64%)

0.93 hits per line