String start/end detection+display in some macros buggy if they contain an open curly brace

[Clockwork-Muse]

cc: @AltSysrq , @Centril

I'm posting this here because I believe the issue to be due to the extension, even though I'm encountering it while working with proptest

Essentially, while specifying a string regex for some of my test cases, using an opening curly brace ({) results in the string detection to skip the next encountered quote mark, resulting in the appearance that additional data is part of the string:

Note that this affects the display only, the code compiles and runs just fine. For that matter, no problems are detected either. This is a cosmetic issue only, no workarounds required.

[nrc]

THis would be a problem in the syntax highlighter which is shipped with VSCode itself. I think this was taken from Atom. I'm pretty sure they would take a PR fixing this, if not we could ship our own highlighter with a fix.

[Clockwork-Muse]

I dunno. I know it's not just any string with curly braces in it, but haven't looked for all factors that might trigger it.