That’s not actual code though, it looks like some kind of trace. Notice the filenames at the end of each line.
The actual solution the issue opener there might be looking for is to disable C++ parsing, since it’s not actually C++ code, it’s just some text they pasted into VSCode and they’re wondering why their editor can’t handle it.
Without thinking about it much, my understanding was that each line of the stack trace referred to a real line, even though the block as a whole wasn’t a program.
But! because of this comment I went and checked the lines of those stack traces. And in fact, they’re not real lines, just the C++ type expansion.
That said I’ve got a another half as bad example that is real so Ive edited the comment to point to that example instead.
If you think that’s good, then you’re gonna love this “simplified” real code posted as a real issue on one of my Github repos.
Edit: updated link to address the stack-trace comment
That’s not actual code though, it looks like some kind of trace. Notice the filenames at the end of each line.
The actual solution the issue opener there might be looking for is to disable C++ parsing, since it’s not actually C++ code, it’s just some text they pasted into VSCode and they’re wondering why their editor can’t handle it.
Without thinking about it much, my understanding was that each line of the stack trace referred to a real line, even though the block as a whole wasn’t a program.
But! because of this comment I went and checked the lines of those stack traces. And in fact, they’re not real lines, just the C++ type expansion.
That said I’ve got a another half as bad example that is real so Ive edited the comment to point to that example instead.