Repository navigation
docs(defaults guard): name the Tunable helper forms the exact match does not see - #33321
Conversation
…oes not see #33161 matches a Tunable helper by the call that can reach it. Its review found five forms that this match misses and the old name match caught. No helper in the tree is called in these ways today. The lead decided to leave them and to write them down where the match is.
|
cmux status (one comment, edited in place; each line is updated by the job that owns it) Review App of this head (app.zip, kept 1 day)
Default changesThis pull request changes 1 default at
Signed off on this commit by Merge receipt: merged as Regenerate the snapshot with Shipped in:
|
|
Review (independent-subagent): SHIP at 1965b23
|
Summary
A comment only, in
tunable_source_defaults. It lists the forms of Tunable helper call that the exact match from #33161 does not see:X.selfT.pointsclass funchelperThe #33161 review found these forms. No Tunable helper in the tree is called in these ways today, and the lead decided to leave them.
This edit changes the guard file, so the defaults guard lists it as a change and needs a receipt.
Observed / Not run
python3 tests/test_defaults_guard.pypasses (73 tests).prepush-gate.pyis clean.Changelog
none
Open in [code]smith · Need help on this PR? Tag
@codesmith-botwith what you need.Summary by cubic
Adds a comment in
tunable_source_defaults(scripts/ci/defaults_guard.py) documenting the Tunable helper call forms that the exact match from #33161 doesn't see: a conformance or superclass declared in another file, inheritance more than one level deep, a nested generic clause, a typealias or localX.self, a helper reached through a generic parameter (T.points), and aclass funchelper. No Tunable helper uses these forms today, so they remain unsupported. Editing the guard file also makes the defaults guard list it as a change requiring a receipt.Written for commit db5d409. Summary will update on new commits.