Improve the core syntax notation capabilities

[user-982634]

Summary

See sublimehq/Packages#1600 (comment)

Expected behavior

Code should be highlighted properly.

Actual behavior

Currently, sublime is unable to properly parse the code. See the linked issue and the relevant comments for details.

Steps to reproduce

1. Open the linked issue
2. Copy some of the test cases
3. Paste to the sublime text editor

Environment

(irrelevant)

[Thom1729]

I'm not sure that this issue is sufficiently specific. Most of the listed bugs have already been fixed in PRs or have been identified as fixable. Of the remainder, some would benefit from nondeterministic parsing, and others would benefit from parameterized contexts. Rather than having one blanket issue for two unspecified features, each should be specified separately.

For nondeterministic parsing, there is an issue already open with a detailed proposal. If you have something to add, or if you feel that a different solution would work better, then I invite you to comment on that issue.

I am not aware of an extant issue regarding parameterized contexts, but there is some discussion of the idea on the Sublime forum. I might eventually get around to writing this up as a more formal proposal, though I'd like to create a reference implementation first.

[user-982634]

Sorry, I'm not a mathematician. The terms like non-deterministic context-free syntax or parametrized contexts mean nothing to me. The purpose of this issue is just to make sublime's core team aware that some issues are unfixable using the current syntax notation.

However, if this is a duplicate of #2241, I think we can close this issue as a duplicate of that one.

[FichteFoll]

if this is a duplicate of #2241, I think we can close this issue as a duplicate of that one.

I believe very much so.