muslrust
rust.vim
muslrust | rust.vim | |
---|---|---|
5 | 23 | |
887 | 3,797 | |
- | 0.7% | |
7.7 | 0.0 | |
2 months ago | about 1 month ago | |
Rust | Vim Script | |
MIT License | Apache License 2.0 |
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.
muslrust
-
Outlook in the terminal
That's isn't true, one can make fully independent static binary in rust
-
Idiot's guide to a Docker deployment?
The winning combo that I found works great is a multistage build, using clux/muslrust to build the dependencies + the binary itself, then using a scratch image as the final stage. Depending on the complexity, the statically linked images I use range from ~9MB to ~22MB. The 9MB image was ported from an existing container that was dynamically linked, and if I remember right, the image was in the ~70-80MB range using debian:buster-slim as the final stage.
-
Guidance about cross compilation tools, especially targeting musl
muslrust: seems to be active last commit on Oct 2, 2021. But what is the difference compared to the one above?
-
"internal compiler error: failed to process buffered lint" with actix-http, only on linux on azure pipeline
Oh, I remember that I use https://github.com/clux/muslrust and is there what the bug is triggered. Weirdly, running it locally not show it.
-
Porting a serverless chatbot from Python to Rust
After a lot of searching I came across a Docker image which provides a clean environment for building Rust linked against musl libc. It includes curl, pq, sqlite3, and zlib, but the main one I needed was OpenSSL. This container image solved my problem and I can run using Docker locally as well as in the GitHub Action build workflow.
rust.vim
-
How to prevent rust-analyzer (rust lsp) from checking code on each save
I am using rustaceanvim and rust.vim.
-
Issue with syntax highlighting in rust with rust-analyzer
When the file first loads, it uses the syntax defined in the $VIMRUNTIME/syntax/rust.vim file from rust.vim, which is what I want, but after a few seconds (probably once rust-analyzer loads and runs), it changes the highlighting to use different colours (there's probably a better way to describe it, but a video is easier to show). This colour change also happens when I write the file (and rust-analyzer runs again).
-
Can’t run specific test via LSP
Or this https://github.com/rust-lang/rust.vim, it has example with running tests
-
Struggling to get basic diagnostic working with LSP
If you need basic syntax checking on leaving insert mode (without saving file), https://github.com/rust-lang/rust.vim can be used
-
Is it possible to have Rust doc test comments highlighted in Neovim?
Seems like there's a tree-sitter solution, but I do want to note that this works out of the box with rust.vim: https://github.com/rust-lang/rust.vim/issues/63. It might be the built-in Rust support is out of date -- using that repo as a plugin would do the trick.
-
Default mappings override user mappings in Rust ( [[ and ]] mappings )
Most of the customizations in the $VIMRUNTIME's rust ftplugin are guarded behind a flag (g:rust_fold, g:rustfmt_autosave,g:rust_recommended_style, etc.) to control enabling and disabling them, but for some reason the navigation mappings are unconditionally defined, with no flag to turn them off... It might be worth going through the issues in https://github.com/rust-lang/rust.vim to see if that ever came up before.
-
Config For rust dev
Is having rust.vim necessary if I'm using rust-tools already?
-
Need help for setting up neovim.
Primeagen has a series, you could also try spacevim or lunarvim( i prefer lunarvim). If you want to read the docs and setup yourself 1. lsp and code completion mentioned in #5. 2. treesitter 3. lsp handles that, you have to install java's lsp, this improves its look. 4. Make your own remaps, some languages have a plugin for this but i can't find one for java, this is the one for rust. 5. Install cmp and one of the snippet engines.
-
Rust with Vim
writing rust is the same regardless of which editor you use and using vim is the same regardless of what programming language you are in, so i dont think you need a tutorial neccissarily. ive been using this plugin for rust-specific features https://github.com/rust-lang/rust.vim
-
Configure NeoVim for Rust Dev
As for plugins for Rust development, I’d recommend Conquer of Completion (using the coc-rust-analyser coc plugin), Rust lang’s rust plugin, and the Toml plugin
What are some alternatives?
rust-musl-builder - Docker images for compiling static Rust binaries using musl-libc and musl-gcc, with static versions of useful C libraries. Supports openssl and diesel crates.
Clippy - A bunch of lints to catch common mistakes and improve your Rust code. Book: https://doc.rust-lang.org/clippy/
rust-musl-cross - Docker images for compiling static Rust binaries using musl-cross
coc-rust-analyzer - rust-analyzer extension for coc.nvim
upx-action - Strips and runs upx on binaries
doom-emacs - An Emacs framework for the stubborn martian hacker [Moved to: https://github.com/doomemacs/doomemacs]
oasis - a small statically-linked linux system
YouCompleteMe - A code-completion engine for Vim
rab - Rusty Armor Builds - Monster Hunter Rise Armor Set Creation Tool
Rustlings - :crab: Small exercises to get you used to reading and writing Rust code!
aws-lambda-rust-runtime - A Rust runtime for AWS Lambda
refactoring.nvim - The Refactoring library based off the Refactoring book by Martin Fowler