structwalk: drop the upper-bound field-count assertion that churns on SDK bumps#5778
Conversation
… SDK bumps The upper bound on the number of fields WalkType discovers has no real integrity value: it only loosely approximated "the walk didn't explode", and every few SDK bumps adds enough fields to push the count past the ceiling, forcing a churn-only edit to a magic number. Drop the maxLen parameter and its assert.Less from testStruct. The properties that matter are kept: the lower bound still catches a walk that silently truncates, the present checks confirm specific fields are reachable, and the notPresent checks still verify circular references terminate at one level - which is the precise guard the upper bound was only gesturing at. Co-authored-by: Isaac
denik
left a comment
There was a problem hiding this comment.
would be simpler to just set it to 100_000
Co-authored-by: Jan N Rose <janniklas.rose@gmail.com>
can you drop all this? title already explains it. |
Integration test reportCommit: 1be1cb6
21 interesting tests: 13 SKIP, 7 KNOWN, 1 RECOVERED
|
No description provided.