On Wednesday, April 3, 2019 at 9:50:31 AM UTC-3, Norbert Melzer wrote: > > You said, you haven't elaborated on tree-parsers benefits, as you think > the linked page did a better job than you could. > > But the web page tells me about nothing. > > On the first paragraph it looks like if it wants to be a modern > replacement for YACC/BISON, not even telling us, what language it can > generate code for. > > One or two paragraphs later, it looks more as if it wants to be a language > server, but with a different protocol and less features. > > As we already have elixir-ls, and it does its job pretty well and > LSP-clients exist for every major editor, I do not think, we need just > another editor plugin. >
To my knowledge a LSP server is not a monolith a bunch of features coded into it - it's simply meant to be a service that complies to the protocol. Any LSP server could make use of Tree-Sitter underneath (or any other tool for that matter). Tree-Sitter's parsed nodes *can *be used for things like autocompletion but that's beside the point. It doesn't do contextual analysis or anything of the sort (as it can be read here <https://github.com/tree-sitter/tree-sitter/issues/244#issuecomment-443482205>). It simply parses and classifies tokens based on the grammar given, and only for the document supplied. Granted, this proposal is not even for a plug-in, IDE integration or anything of the sort. It's meant to be a call for action on building a grammar that could be used in editors. I had the idea to bring it here first because the core team is more likely to understand the grammar (and it's ambiguous/corner cases) better. > Also, as the core team denied to take the LS under the org, I think, 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 <javascript:>> wrote: > >> 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. >> >> >> ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ >> >> https://tree-sitter.github.io/tree-sitter/#available-parsers >> >> It seems like Elixir is not in the roadmap for language support. >> >> Atom has the most complete implementation currently. I expect other >> editors (e.g. Vim, VSCode, Emacs, etc...) to follow in adoption when the >> API stabilizes and more bugs are fixed. >> >> Project: https://github.com/tree-sitter/tree-sitter >> Neovim: https://github.com/neovim/neovim/pull/9219 >> Emacs: https://github.com/karlotness/tree-sitter.el >> VSCode: https://github.com/Microsoft/vscode/issues/50140 >> >> Example grammar for Javascript - >> https://github.com/tree-sitter/tree-sitter-javascript/blob/master/grammar.js >> >> -- >> You received this message because you are subscribed to the Google Groups >> "elixir-lang-core" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to elixir-l...@googlegroups.com <javascript:>. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/elixir-lang-core/899f266d-6506-4aa6-bf31-0807a6d82786%40googlegroups.com >> >> <https://groups.google.com/d/msgid/elixir-lang-core/899f266d-6506-4aa6-bf31-0807a6d82786%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> For more options, visit https://groups.google.com/d/optout. >> > -- You received this message because you are subscribed to the Google Groups "elixir-lang-core" group. To unsubscribe from this group and stop receiving emails from it, send an email to elixir-lang-core+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/elixir-lang-core/14f07104-f823-4e12-a09a-91f8848a3b7e%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
