language-servers/erlang-language-platform
1
0
Fork 0
mirror of https://github.com/WhatsApp/erlang-language-platform.git synced 2025-12-23 12:26:48 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions

Fix typo in FAQ (#2)

Browse source 
Summary:
Hopefully you can appreciate a 1-char fix :-)

Pull Request resolved: https://github.com/WhatsApp/erlang-language-platform/pull/2

Reviewed By: michalmuskala, TD5

Differential Revision: D48028930

Pulled By: alanz

fbshipit-source-id: cd9087aeaa727d0c6eef9ecd31c9b6f11bb608cc
This commit is contained in:
Onno Vos 2023-08-03 04:26:33 -07:00 • committed by Facebook GitHub Bot
parent 239de4c9c1
commit 2bcbb4cc40
1 changed files with 1 additions and 1 deletions
Download patch file Download diff file Expand all files Collapse all files

2
FAQ.md
View file

@ -15,6 +15,6 @@ Erlang LS acts as the "glue" between existing OTP tools (Compiler, EDoc, XRef, e
There are a few reasons for our choice:
* ELP required two big components to exist: a parser generator with good error recovery and a framework for incremental computation. Both compoonents (respectively [Tree Sitter](https://tree-sitter.github.io/tree-sitter/) and [Salsa](https://github.com/salsa-rs/salsa) are available for Rust but not yet for Erlang
* ELP required two big components to exist: a parser generator with good error recovery and a framework for incremental computation. Both components (respectively [Tree Sitter](https://tree-sitter.github.io/tree-sitter/) and [Salsa](https://github.com/salsa-rs/salsa) are available for Rust but not yet for Erlang
* The LSP libraries for Erlang are only partially implemented (as part of Erlang LS), while they are complete for Rust
* ELP is modeled after Rust Analyzer, which is itself implemented in Rust. Having a widely used reference was extremely helpful during development