Re: [elixir-core:8591] [proposal] Tree-Sitter grammar parser for Elixir

2019-04-03 Thread João Paulo Silva de Souza
they > should deny to do so for this as well, for the same reason they had for the > LS last year. (TLDR: burden of maintenance is to high). > > On Fri, Mar 29, 2019 at 3:10 AM João Paulo Silva de Souza < > joao.paul...@hotmail.com > wrote: > >> Seems like I wrongly

[elixir-core:8586] Re: [proposal] Tree-Sitter grammar parser for Elixir

2019-04-03 Thread João Paulo Silva de Souza
until VSCode & friends are all fully integrated into it. On Thursday, March 28, 2019 at 11:10:14 PM UTC-3, João Paulo Silva de Souza wrote: > > Seems like I wrongly opened an issue instead of posting here first -> > https://github.com/elixir-lang/elixir/issues/

Re: [elixir-core:8585] Re: [proposal] Tree-Sitter grammar parser for Elixir

2019-04-03 Thread João Paulo Silva de Souza
What exactly are those effects that could pose issues? Nested macro blocks inside of another macro? Ambiguous syntax due to macro usage? IMO Tree-Sitter will be at least as correct as current RegExp syntaxes, while being faster, with the upside of potentially turning out much better. The worst

[elixir-core:8583] Re: [proposal] Tree-Sitter grammar parser for Elixir

2019-04-03 Thread João Paulo Silva de Souza
> What are you proposing? > > On Thursday, March 28, 2019 at 10:10:14 PM UTC-4, João Paulo Silva de > Souza wrote: >> >> Seems like I wrongly opened an issue instead of posting here first -> >> https://github.com/elixir-lang/elixir/issues/8917. >> >>

[elixir-core:8559] [proposal] Tree-Sitter grammar parser for Elixir

2019-03-28 Thread João Paulo Silva de Souza
Seems like I wrongly opened an issue instead of posting here first -> https://github.com/elixir-lang/elixir/issues/8917. My reasoning is that this is not a language feature and thus I thought I could skip the proposal process. My apologies.