fix: scope CC016 awaits to their owning function#33
Merged
Conversation
An await inside a nested lambda or local function does not make its synchronous container asynchronous. Respecting function boundaries prevents false unused-token diagnostics while retaining capture-aware token usage.
This was referenced Jul 21, 2026
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
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
Why
The previous unrestricted descendant search made a synchronous outer method look asynchronous when only a nested function performed awaited work, producing a false unused-token diagnostic.
Validation
Tooling note
Slopwatch is required by the local .NET overlay but unavailable on this host (
command not found). Manual hygiene and exact-diff review are clean.