Distinguish finite slice views from cycles
This commit is contained in:
@@ -139,6 +139,9 @@ Focused check: `go test ./internal/engine -run 'Dynamic|Projection|Clone|Resolut
|
||||
Finding: **A03**.
|
||||
Owners: `internal/engine/value_operation.go`, `value.go`, `clone.go`, and tests.
|
||||
|
||||
Status: **complete** (A03). Prior stage commits: `2736ddf`, `deb9aa5`.
|
||||
Validation passed: `GOTOOLCHAIN=local GOPROXY=off GOTELEMETRY=off go test ./internal/engine -run 'Mapping|Value|Projection|Clone|Override|Cycle|FiniteSlice|SliceCycles' -count=1` and `GOTOOLCHAIN=local GOPROXY=off GOTELEMETRY=off go test ./internal/engine -count=1`.
|
||||
|
||||
Add visible slice length to `valueVisit` identity in `visitFor`. Keep type, kind,
|
||||
and starting pointer, existing empty/nil handling, and active-path removal on
|
||||
unwinding. Capacity is not part of the visible traversed graph. Maps and pointers
|
||||
|
||||
Reference in New Issue
Block a user