[BUG] `"//"` `"/*"` inside string literal treated as real comment and doesn't compile

[realgdman]

Describe the bug
`"//" "/*" symbols inside string literals treated as comment start and break compilation, like shadowing closing }
For // it happens inside { block }

To Reproduce
https://cpp2.godbolt.org/z/5KEPj196s
Uncomment lines marked as error

main: () = {
	std::cout << "//123"; //123, ok
	//{ std::cout << "//456"; } //error

	:()->_ = "//Ok";
	//:()->_ = { return "//Error"; }

	a:="*/ ok";
	{ c:="*/ ok"; }
	//b:="/* error even without {} block";
}
//error: (x) = { return "//"; }

Version
latest
Command lines
cppfront/cppfront $1.cpp2 -p
clang++-15 -Icppfront/include $1.cpp -std=c++20 -o $1

Expected result
Success compilation and usage of such string literals
Actual result/error
call.cpp2(32,0): error: end of file reached with 1 missing } to match earlier { on line 1

Additional context
I've encountered this inside lambda, when expanding it and changing short syntax to code block. Then discovered "/*" have same issue even without block.

"*/" doesn't seems to have problem.

[hsutter]

Reopening as a reminder to handle the raw string literal case too...

[JohelEGP]

Of course, '\\\n' is not a valid string literal.
Does this deserve a different issue? See https://cpp2.godbolt.org/z/e7eWbjPjv:

  _ = $R"(((_ = s.split('\\\n'), 0))$)";

main.cpp2...
main.cpp2(5,35): error: character literal '\\\' is missing its closing '
main.cpp2(5,40): error: character literal '),' is missing its closing '
main.cpp2(5,26): error: unexpected text - expression-list is not terminated by ) (at '=')

[tattwamasi]

raw string literals with () in them also fail like this and apparently {} ( per #841 )

[tattwamasi]

I wanted to clarify that the parenthesis causing a compile error are only if they are not on the same initial line as the start of the raw string, and (this is odd) only if it is at file scope level rather than inside a function.

For example, consider your raw string regression test:
https://github.com/hsutter/cppfront/blob/9f7bd9fc865d70d5b5309f23ebdc29db932bf3e2/regression-tests/pure2-raw-string-literal-and-interpolation.cpp2

If you add some parenthesis to the raw_str_multi, for example on line 13, insert "( has parens)" at the beginning.
The test still works.
Now do it at file scope. It fails.
Put the parens on the same first line as the R string start and it works. It's the open paren that actually triggers it. Close parens can be in the string.

example declaration and definition - stick an open paren in the string's 2nd or subsequent line to see compile error:
raw_str_multi_filescope : std::string = R"test(this is raw string literal

that has no parens inside) and can last for multiple

lines)test";