Nelo Mitranim
Nelo Mitranim
Currently the syntax prioritizes support scopes at the expense of other roles, such as function calls or constructor calls. For example: ```js console.error // ^^^^^ support.function.console - variable.function console.error(err) //...
The content of tags in JSX/TSX is basically a string. It would be nice to give color schemes an option to visually color it as such: ```jsx // Source: some...
Currently, literals accept options such as scope names, but rules don't. Seems like an omission. It would be very useful to define a rule and instantiate it with different scopes...
Currently SBNF doesn't seem to support inheritance or imports between syntaxes (unlike `.sublime-syntax` with `extends`). For some syntaxes, this would be quite a useful feature. Currently SBNF requires all definitions...
For some recursive or mutually recursive rules, the resulting code has redundancies that a human-written version wouldn't have. Unfortunately I'm too inexperienced to tell whether it's SBNF or my rules....
Jisp needs a comprehensive compiler test suite. It turned out that recompiling itself is far from being a good enough test.
With nested macros, it’s possible to have an array of things you want to give to an inner macro as arguments. ToDo implement `(spread)` support for macro calls.
The `#n` and `#` notation needs to support the following: - ~~`.dot` and `[bracket]` property notation (the current workaround is the `(get #n prop)` or `(do #n (.stuff))` notation)~~ (fixed...
Right now, in a code returned from a macro, regex property notations like `/regex/.text` render as `[native code]`. ToDo fix. The current workaround is to use the `(get /regex/ property)`...