hpack
Rust Language Server
DISCONTINUED
Our great sponsors
hpack | Rust Language Server | |
---|---|---|
4 | 6 | |
607 | 3,568 | |
- | - | |
6.2 | 7.0 | |
4 months ago | over 1 year ago | |
Haskell | Rust | |
MIT License | GNU General Public License v3.0 or later |
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.
hpack
-
[RFC] Generate Cabal files from TOML
There are ways to get around this, but it's not easy and doesnt scale: https://github.com/sol/hpack/issues/194
-
Haskell as a first timer - Am I missing something ?
The yaml you are talking about is part of a tool called hpack. This tool can be used on it's own (and with cabal-install as such), it just so happens that stack has it's own internal copy of it and runs it automatically whenever it finds a package.yaml.
Rust Language Server
-
Why doesn't rust-analyzer reuse infrastructures of rustc?
In the last there was RLS that did exactly that. But the approach of rust-analyzer was found to be more performant.
-
[RFC] Generate Cabal files from TOML
LSP support seems to be lacking as well, at least rust doesn't seem to have Cargo.toml support? https://github.com/rust-lang/rls/issues/785
-
friendly reminder for our vscode folks, use rust-analyzer
Why: The rust-analyzer extension integrates with rust-analyzer, an alternative language server for Rust. rust-analyzer tends to perform better and get less confused with your code as compared to RLS, which the Rust extension uses.
-
Show HN: Skruv – No-dependency, no-build, small JavaScript framework
I have tried writing websites with rust instead of JavaScript. Unfortunately, the tooling is just not there. More specifically, I am talking about wasm-bindgen, which provides two-way bindings. The problem with it is that since all the declarations are generated with build.rs, there is no autocompletion. Since I am spoiled by modern tooling, no autocompletion to me means not feasible pass demo stage. (https://github.com/rust-lang/rls/issues/1489)
Aside from the lack of autocompletion, passing rust closures to js land (DOM) is extremely janky as well. However, that might be caused by my lack of experience with rust.
(If you are curious, this is what I made: https://github.com/SCLeoX/non-grid-path-finder)
What are some alternatives?
Rustup - The Rust toolchain installer
Racer - Rust Code Completion utility
rusty-tags - Create ctags/etags for a cargo project
rust-analyzer - A Rust compiler front-end for IDEs
semantic-rs
AlgorithmW - Example implementation of Algorithm W for Hindley-Milner type inference
artifact - The open source design documentation tool for everybody
Clippy - A bunch of lints to catch common mistakes and improve your Rust code. Book: https://doc.rust-lang.org/clippy/
bumper - Haskell tool to automatically bump package versions transitively.
coc.nvim - Nodejs extension host for vim & neovim, load extensions like VSCode and host language servers.
castle - A tool to manage shared cabal-install sandboxes.
hdocs - Haskell docs tool