Repository navigation
Replies: 1 comment 2 replies
LSP's most common input is about in-complete code, which for Lisp is unbalanced parenthesis and unexecutable S-expression in REPL. Scheme-langserver's main idea is Principle of Least Astonishment, that code should behave as its name and interface most obviously imply, minimizing surprise for the reader. So, this project supposes programmers won't surprise itself, for which you may refer to analysis/abstract-interpreter.sls: According to its context, though it may not aims to be determined but specific semantic meaning is truly determined and processed in analysis/identifier/rules and other rules.
Many counterparts can do this, including many VScode plugin. But as for scheme-langserver, it firstly serves as an language server defined by LSP(Language Server Protocol), which doesn't require REPL function, so that scheme-langserver doesn't implement REPL. You may not notice that incomplete code can't be digested by REPL. REPL is not the God, and scheme-langserver aims to do what the God can't do. |
Uh oh!
There was an error while loading. Please reload this page.
You've said
Geiser can only complete top-level bindings listed by environment-symbols (on Chez Scheme) or raw symbols—not true identifiers. This means local bindings and unfinished code receive no help in recognizing valid identifier scopes. The same limitation applies to goto definition and other core IDE features.
I want to know how do you solve these problems.
Geiser can communicate withe scheme repl, can your lsp do the same thing?
I have been envisioning creating a REPL for Chez that runs code and provides information like the live range of variables.
All reactions