You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Give every config entry point the decode hint, not three of five
Reviewing the commit that added the hint found it had done to itself
exactly what it was fixing: bytes reached Lexicon's vocabulary fields
and Policy's collection fields with a decode hint, while
capitalization_exceptions and name_order still reported the cryptic
byte value ("name_order elements must be Role members, got 103" -- 103
is 'g'). Guarding one member of a family and leaving its siblings is
the most repeated defect on this branch; that is now three rounds.
Also widened to bytearray and memoryview. bytes was the only binary
type checked, so memoryview(b'ab') still surfaced "got 97".
One shared _reject_buffer() in _lexicon, called from both entry points,
and the same check on all three Policy/PolicyPatch sites. The tests
are parametrized over every entry point x every buffer type rather than
one example each -- a per-example test is what let the gap through.
The perf-shape coverage table said "at n=200"; the test runs at 800.
Re-measured: the columns are identical at both, so the note now cites
the base it is actually describing.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
0 commit comments