Repository navigation
docs: v1.146.0 — x-FuSa spec v1.15.2, §1.6.1 Rule A false-positive tradeoff - #102
Merged
Merged
Conversation
…adeoff A same-day ada-FuSa self-review (issue #101) flagged the bracket/"TBD"- substring deny-list as occasionally false-positiving on legitimate engineering prose and asked whether that was intended. It is — the spec now states the tradeoff explicitly with both examples (buffer[i], STBD) so future audits hit the documented answer instead of re-deriving it. Pure documentation addition, no behavior change. Signed-off-by: SoundMatt <SoundMatt@users.noreply.github.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Closes #101.
A same-day ada-FuSa self-review flagged Rule A's bracket/
"TBD"-substring deny-list as occasionally false-positiving on legitimate engineering prose (buffer[i], the abbreviation"STBD") and asked whether that was intended. It is — the spec now states the tradeoff explicitly with both examples, so a future audit hits the documented answer instead of re-deriving it. Pure documentation addition, no behavior change — hence a PATCH bump (1.15.1 → 1.15.2).Test plan
go build ./...,go vet ./...,go test ./...clean