spec - naked_strings_in_body

Referenced by1

Labels1

Idea	Status	Tags	Summary	Katz
comments	done		Line comments use `//` through end of line ( hidden `SL_COMMENT` ). Block comments use `/* … /` and may span multiple lines ( hidden `ML_COMMENT` ). Meta comments on the same line after content are allowed ( `keep this // meta` ). Comments must not open inside a string / reference-string context: - Naked body quotes ( ["naked_strings_in_body"] ): a quoted slash-slash that is not a comment, quoted urls, `"../mod//.rq"`. - Reference / import `STRING` paths ( `["…"]`, `from "…" import …` ) — the lexer consumes the whole quoted path as one `STRING`, so neither `//` nor `/` inside the quotes starts a comment. Example: a file reference whose path text contains slash-slash, `["../extension//.rq".webview]`. - URL / path-segment guard: `//` immediately after `:` or `/` is not a line comment. Same-line fences: ["./syntax-edge-cases.rq".fencing_comments] — complete `"…"`, `'…'`, and ` ` ` … ` ` ` spans keep ` Unclosed quote or backtick openers are not fences, so `//` after them is a comment. Comment-range identity across lexer, scanner, and TextMate: ["../core_analysis/rust_port.rq".comment_span_align]. Multiline / glob clash: the empty block form `//` is not a comment — it is the recursive glob segment used in paths such as `../mod//.rq`. A real block comment needs a non-empty body ( `/ note /`, `/\n note\n/` ). The token builder rejects length-4 `/*/` matches; comment-span scanners skip the same sequence so embedded `rq:[…]` discovery stays aligned. Related: [comment_reference_ignore], [string_literals], ["./imports.rq".wildcard_references], ["../core_analysis/rust_port.rq".comment_span_align].	0.145

Reference labels

"naked_strings_in_body"