style: remove redundant comments across the codebase (cleanup sweep)#1737
Merged
Conversation
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.
Removes 439
//comments that only restate the adjacent code (e.g.// Split into linesabove acomponents(separatedBy:),// Increment counter,// Handle column count mismatch), across 110 files. This is the broad pass following batch 1 (#1736).Safety
The change is comment-only. Verified mechanically, not by eye:
main(0 mismatches across 110 files). No code line was added, moved, or altered.///doc comment,// MARK:marker, file header, or// swiftlint:directive was removed.code // notebecomescode).What was kept on purpose
1,977 comments were reviewed and left in place: anything documenting a non-obvious why, an invariant or ordering requirement, a workaround or footgun, a binary/wire format (ASN.1/PKCS layouts in BigQuery auth), or a step that makes a tricky parser or state machine followable. The keep-to-remove ratio (1977:439) reflects that most comments here carry real information.
No CHANGELOG: internal, no user-facing change. Happy to split this into per-area PRs (Core / Views / Plugins) if you'd prefer smaller reviews.