Skip to content

fix: preserve evidence after C# raw string literals - #34

Merged
bewaterhere-coder merged 2 commits into
mainfrom
fix/csharp-raw-string-comment-boundary
Nov 1, 2026
Merged

bewaterhere-coder merged 2 commits into
mainfrom
fix/csharp-raw-string-comment-boundary

Conversation

@bewaterhere-coder

Copy link
Copy Markdown
Owner

Summary

  • Recognize C# raw string literals with three or more quote delimiters before ordinary string/comment matching.
  • Prevent // inside a raw string containing embedded quotes from hiding later code on the same line.
  • Add a regression test that verifies real code after the raw string remains visible while a true trailing comment is ignored.

Why

C# 11 raw strings may contain unescaped quote characters. The previous regular-string pattern could terminate early, then treat // inside the remaining raw-string content as a comment start and erase subsequent code evidence.

Boundaries

  • This remains a bounded literal scanner, not a full C# parser.
  • No change to Lua handling, token semantics, or advisory status definitions.
  • No public API or schema version change; all findings remain non-blocking.

Validation

Python 3.10–3.13, MCP stdio E2E and Sample Project Advisory.

@bewaterhere-coder
bewaterhere-coder merged commit cf6c822 into main Nov 1, 2026
6 checks passed
@bewaterhere-coder
bewaterhere-coder deleted the fix/csharp-raw-string-comment-boundary branch November 1, 2026 01:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant