Feasability Assessment: Extension to decorate conflict markers

VS Code uses TextMate grammars, which underneath run a buncha regex (which explains its performance characteristics hah), while CM (usually) uses Lezer, which is an LR-parser, so the grammars are pretty different. However, Lezer has good error recovery, so it too should be able to parse a document with conflict markers… as long as the conflicts are between complete statements/expressions, as in your screenshot. A more complex multi-line conflict that occurs inside or between statements/expressions may have… odd behavior. Like, a conflict line of just

.FirstOrDefault()

isn’t a complete statement/expression so IDK how a parser would be able to handle it without context.

Here’s a demo of some conflict markers in JS using https://lezer-playground.vercel.app/

The code is pretty nonsensical don’t think too hard about it.

Would it necessarily be an inherently bad idea to have a block-level widget that hosts three small nested CM editor views?

That’s outside my experience, unfortunately. However a search of the forums reveals one user who says they got 3 levels of nested CM6 working.