What an odd name for a programming language. I’m working on two different programming languages but both share one aspect, they are compiled to Rust. One is called Darcy lang and uses S-expressions the other is called Quiche and it brings a Pythonic flavour to Rust programming (and removes the borrow/ownership boilerplate from the language).
Both makes certain assumptions, but Darcy uses minimal abstractions and translates nearly 1:1 (does not support explicit traits though). Quiche is a tad bit slower than Rust (~80-85%) in performance but you win in terms of developer productivity and keep the same safety checks as Rust. Both are 100% safe.
Getting the LSP working for either of them has been more challenging than I imagined. Quiche affords me more choice because of the fantastic Ruff project. I am already heavily relying on their AST with Rust types latched on and an additional compiler pass for adding native support for discriminated enums.
Anyway, I think the space is particularly challenging for non-interpreted languages as they lack the real-time introspection necessary to do this. So additional infrastructure is required to basically, rebuild parts of the compiler to be more interpreter like. Just wanted to share some background on the complexities surrounding this stuff.
"language server" is probably not particularly obscure (or random) to the audience of people who know what "mecrisp-stellaris" is (i.e. the audience of the post).
i actually doubt "language server" is obscure to pretty much anyone who has done any programming recently.
What an odd name for a programming language. I’m working on two different programming languages but both share one aspect, they are compiled to Rust. One is called Darcy lang and uses S-expressions the other is called Quiche and it brings a Pythonic flavour to Rust programming (and removes the borrow/ownership boilerplate from the language).
Both makes certain assumptions, but Darcy uses minimal abstractions and translates nearly 1:1 (does not support explicit traits though). Quiche is a tad bit slower than Rust (~80-85%) in performance but you win in terms of developer productivity and keep the same safety checks as Rust. Both are 100% safe.
Getting the LSP working for either of them has been more challenging than I imagined. Quiche affords me more choice because of the fantastic Ruff project. I am already heavily relying on their AST with Rust types latched on and an additional compiler pass for adding native support for discriminated enums.
Anyway, I think the space is particularly challenging for non-interpreted languages as they lack the real-time introspection necessary to do this. So additional infrastructure is required to basically, rebuild parts of the compiler to be more interpreter like. Just wanted to share some background on the complexities surrounding this stuff.
The language here is Forth, the odd naming is for a specific implementation.
> everyone knows what <obscure set of random words> are by now
whatever
><obscure set of random words>
"language server" is probably not particularly obscure (or random) to the audience of people who know what "mecrisp-stellaris" is (i.e. the audience of the post).
i actually doubt "language server" is obscure to pretty much anyone who has done any programming recently.