deathaxe
deathaxe
I don't think so.
@wbond Can this be labeled RFC?
@FichteFoll @keith-hall : How to sort `switch` and `case` like statements into the tree? I saw different solutions like - C/C++, D, Go, `keyword.control` - C#, JavaScript `keyword.control.switch`, `keyword.control.switch.case` -...
This would mean to scope all kinds of loops (i.e. `while`, `for`, `repeat`, ...) with `keyword.control.loop.begin` if the keywords are used to open a loop statement. Keywords like `until`, `end`,...
> I favor option 1. Me too. > Here's an update of my most recent proposal regarding the exact scope names. Like it. 1. Maybe add `keyword.control.exception.finally`? 2. I like...
> conditional `keyword` scopes should probably apply to the `punctuation.section.block` character as well. This depends on your color scheme. `if`, `elif`, `else` are of `keyword.control.conditional`, which would not apply to...
I'd vote to add the following scope to the list of defaults keyword: `assert` scope: `keyword.control.exception.assert` idea/reason: An assertion is something like a short `try` block, which raises an exception...
None of the `flow` keywords is followed by an expression to evaluate. They are instead followed by arguments which are returned only. For instance `throw Exception` just creates an object...
> This is my view as well. I'd be more interested in the jump than the cause. Convinced.
> ... there is the panic macro/function in rust/go, It looks very much like the `die` or `dump` in Perl. I assigned `keyword.control.flow.[die|dump].perl` to them, even though they are called...