chalk
eglot
chalk | eglot | |
---|---|---|
25 | 66 | |
1,768 | 2,178 | |
0.6% | - | |
7.0 | 3.0 | |
29 days ago | 4 days ago | |
Rust | Emacs Lisp | |
GNU General Public License v3.0 or later | GNU General Public License v3.0 only |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
chalk
-
Why did Prolog lose steam? (2010)
The Rust compiler uses a Prolog-like query language internally for type checking generic requirements and traits: https://github.com/rust-lang/chalk
-
Why doesn't rust-analyzer reuse infrastructures of rustc?
rust-analyzer already uses chalk (https://github.com/rust-lang/chalk) which should replace the current trait resolver.
-
Why use Rust on the backend? by Adam Chalmers
Well it's quite easy to come to that conclusion: The code compiles with rustc, which is currently the reference implementation. If rust-analyzer does not match rustc's behavior it's an issue in their implementation. That written it's not that easy to fix as it's related to how rust-analyzer resolves types/traits. rust-analyzer uses chalk for this, which is known to be incomplete/diverging from the RFC'ed behavior. Now one could argue that we can simplify diesel to the point where it works will with rust-analyzer/chalk, but that would result in basically removing core diesel features that exist way longer than rust-analyzer.
-
Why has functional programming become so popular in non-academic settings?
> Not all of those things work well in the real world. E.g. logic programming (prolog) is cool but ultimately never really caught on.
It does have its niches though. For example, there is a trait solver for Rust called Chalk that uses a Prolog-inspired language because trait bounds basically define a logic:
https://github.com/rust-lang/chalk
-
General mathematical expression analysis system
Maybe something in the prolog/datalog direction could be useful? Notably Rust has Chalk to help with trait resolution ("Chalk is a library that implements the Rust trait system, based on Prolog-ish logic rules.")
-
Useful lesser-used languages?
There has been work to implement part of the Rust typing logic in the Chalk Engine which uses a prolog-ish syntax to describe its rules.
-
Can you have a function return different types known at compile time
That's something Chalk is trying to tackle.
-
Compile time wins today
We probably will see all of them at some point -- polonius is a current effort to make the borrow checker accept more valid programs, in a way that also simplifies the logic and is probably a bit faster than the current NLL system, chalk is an attempt to do a similar thing for the trait system, and cranelift is a project that seeks to replace the LLVM codegen backend. But obviously, these are very large and complex projects that are gonna take some time.
-
What is the difference between associated types and generics?
Do Rust developers realize that? Oh, yes, absolutely, that's why we have this:
-
Question about Trait Bounds (from Rust for Rustaceans)
For me an attempt to write where HashMap: FromIterator and then use new and insert was totally bizzare because currently rustc is pretty primitive and doesn't do super-complex machinery needed to do what you want. Chalk may fix that one day, but it's nowhere near to being ready for inclusion into rustc thus I wouldn't even attempt to do what you tried to do… but that's not something you are supposed to know before reading this book!
eglot
-
LSP could have been better
Recently I stumbled upon this issue:
https://github.com/joaotavora/eglot/discussions/1127
I don't know enough about emacs and LSP to see the full picture, but it seems that both eglot's and corfu's maintainers, assumably very competent programmers, can't find a solution for this.
I only skimmed the thread. My understanding is that LSP dumps a long list of completion candidates at once and they can't decide a cache strategy that works well with existing code...?
-
Spurious errors with Eglot / pylsp
It could be. There are unfixed issues with eglot and corfu, and sadly not a lot of willingness to investigate.
-
Using Quarto with Emacs
Eglot errors when I add new Python code blocks. The error disappears when I reconnect the language server, but the same happens again when I add a new code block. My "workaround" now is that before I start working on the .qmd file, I just add a bunch of Python code blocks (for which I also have a function) and then reconnect the language server again. This way I can start working for a while until I need to add more code blocks again.
-
Looking for help in improving Typescript Eglot, Corfu, Orderless performance
This discussion has helped with some performance issues: https://github.com/joaotavora/eglot/discussions/993.
-
Typescript highlighting in emacs incomplete (compared to VSCode) even after using treesitter?
I guess eglot doesn't support it yet: https://github.com/joaotavora/eglot/pull/839
-
joaotavora/breadcrumb: Emacs headerline indication of where you are in a large project
This is not by pure chance, João is the developer of the Eglot LSP client and the breadcrumbs from LSP-mode had been requested as a feature, but as far as I remember João thought rightfully that this could be an independent package, see https://github.com/joaotavora/eglot/discussions/988
-
Returning emacs user - what packages are common now?
A substantial section of the community is using corfu instead of company, but I wouldn't say company is out of date by any means. In emacs 29 eglot will be a built in, which might act as a replacement for lsp-mode depending on what functionality you need.
-
Eglot upgrade strategy
I am currently running emacs 29 (built from emacs-29 branch) which – according to https://github.com/joaotavora/eglot – should contain the latest eglot.
-
916 Days of Emacs
Yep. You can use flymake or flycheck for that in combination with eglot or lsp-mode.
See https://github.com/joaotavora/eglot#diagnostics
-
Eglot, eldoc and golang
(I have reported this (that is, ElDoc missing docs for callable things at point, when Eglot is enabled) as an issue recently: First on GitHub-discussions https://github.com/joaotavora/eglot/discussions/1200, then on Debbugs https://debbugs.gnu.org/cgi/bugreport.cgi?bug=62687. But the threads are very long, so I don't recommend reading them.)
What are some alternatives?
polonius - Defines the Rust borrow checker.
lsp-mode - Emacs client/library for the Language Server Protocol
miri - An interpreter for Rust's mid-level intermediate representation
dap-mode - Emacs :heart: Debug Adapter Protocol
prolog - The only reasonable scripting engine for Go.
clangd - clangd language server
lccc - Lightning Creations Compiler Frontend for various languages
rust-analyzer - A Rust compiler front-end for IDEs [Moved to: https://github.com/rust-lang/rust-analyzer]
pny1-assignment - College assignment writing in which I ramble about type classes and dependent types.
web-mode - web template editing mode for emacs
expr - Expression language and expression evaluation for Go [Moved to: https://github.com/expr-lang/expr]
company-mode - Modular in-buffer completion framework for Emacs