fenix
rust-analyzer
Our great sponsors
fenix | rust-analyzer | |
---|---|---|
19 | 207 | |
562 | 9,320 | |
7.1% | - | |
9.5 | 10.0 | |
about 21 hours ago | about 2 years ago | |
Nix | Rust | |
Mozilla Public License 2.0 | 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.
fenix
-
Use nix-shell or systemPackages
Rustup works as is. Though note that Nix supplants all such toolchain installers such as Rustup, nvm, etc. I.e. instead of Rustup there is fenix.
-
Can rustc generate identical binaries, with the same hash, from the same souce code?
Fenix ( https://github.com/nix-community/fenix ) has tooling or picking a specific toolchain or even nightly. You can then build with the following nix code:
- Fenix: Rust toolchains and rust-analyzer nightly for Nix
-
Annoucing fenix monthly, Rust toolchains updated 1st of every month
Fenix monthly is a new branch similar to the main branch, but only updated on the 1st of every month, for cases where you want to use rust nightly but don't need it to be updated very often.
- Fenix - Rust toolchains and rust-analyzer nightly for Nix
- Show HN: Fenix – Rust toolchains and Rust-analyzer nightly for Nix
-
Why this overlay doesn't work?
The issue should be fixed once the nix-vscode-extension and fenix patches are merged. The latter will happen automatically once CI passes.
-
Have a few questions about NixOS
4. I would suggest Mozilla's Rust overlay or fenix or similar instead of Rustup - that would be more of the "Nix-way" to acquire the toolchain and you can still manage multiple versions. Not sure what the Ruby equivalent is, I don't do Ruby.
-
Oops, I Did It Again...I Made A Rust Web API And It Was Not That Difficult
To follow along, you'll need a stable Rust toolchain. See the install page for instructions to install rustup for your platform. You should prefer this method to your distribution's package manager. If you're a NixOS freak, I recommend fenix.
- Fenix: rust toolchains for all channels and rust-analyzer nightly
rust-analyzer
-
rust-analyzer changelog #177
#14561 map tokens from include! expansion to the included file
-
Make LSP-Rust-analyzer works
return { tools = { -- autoSetHints = false, on_initialized = function() vim.api.nvim_create_autocmd({ "BufWritePost", "BufEnter", "CursorHold", "InsertLeave" }, { pattern = { "*.rs" }, callback = function() vim.lsp.codelens.refresh() end, }) end, auto = false, inlay_hints = { -- Only show inlay hints for the current line only_current_line = false, auto = false, -- Event which triggers a refersh of the inlay hints. -- You can make this "CursorMoved" or "CursorMoved,CursorMovedI" but -- not that this may cause higher CPU usage. -- This option is only respected when only_current_line and -- autoSetHints both are true. only_current_line_autocmd = "CursorHold", -- whether to show parameter hints with the inlay hints or not -- default: true show_parameter_hints = false, -- whether to show variable name before type hints with the inlay hints or not -- default: false show_variable_name = false, -- prefix for parameter hints -- default: "<-" -- parameter_hints_prefix = "<- ", parameter_hints_prefix = " ", -- prefix for all the other hints (type, chaining) -- default: "=>" -- other_hints_prefix = "=> ", other_hints_prefix = " ", -- whether to align to the lenght of the longest line in the file max_len_align = false, -- padding from the left if max_len_align is true max_len_align_padding = 1, -- whether to align to the extreme right or not right_align = false, -- padding from the right if right_align is true right_align_padding = 7, -- The color of the hints highlight = "Comment", }, hover_actions = { auto_focus = false, border = "rounded", width = 60, -- height = 30, }, }, server = { --[[ $ mkdir -p ~/.local/bin $ curl -L https://github.com/rust-analyzer/rust-analyzer/releases/latest/download/rust-analyzer-x86_64-unknown-linux-gnu.gz | gunzip -c - > ~/.local/bin/rust-analyzer $ chmod +x ~/.local/bin/rust-analyzer --]] -- cmd = { os.getenv "HOME" .. "/.local/bin/rust-analyzer" }, cmd = { os.getenv "HOME" .. "~/.cargo/bin/rust-analyzer" }, on_attach = require("user.lsp.handlers").on_attach, capabilities = require("user.lsp.handlers").capabilities, settings = { ["rust-analyzer"] = { lens = { enable = true, }, checkOnSave = { command = "clippy", }, }, }, }, }
-
rust-analyzer changelog #164
I would like changes like https://github.com/rust-analyzer/rust-analyzer/pull/13799 to be listed in 'Breaking Changes' category, to приманка draw the users' attention.
-
Mun v0.4.0 released
For those of you who haven’t heard of Mun before, Mun is an embeddable programming language empowering creation through iteration. The idea to create Mun originated out of frustration with the Lua dynamic scripting language and a desire to have similar hot reloading functionality available in Rust. As such, it’s not a direct competitor with Rust, but instead is intended to be used with Rust (or C/C++) as a host/embedded language pairing. Actually, Mun is completely written in Rust, building on similar crates as rust-analyzer and rustc. Its key features include:
-
rust-analyzer changelog #159
#13728 upgrade chalk to make solver fuel work again (works around most trait solving hangs).
-
rust-analyzer changelog #147
#13221 (first contribution) add option to move lenses above doc comments (rust-analyzer.lens.location):
-
Does Rust need proc-macros 2.0?
Rust-analyzer has a good overview: https://github.com/rust-analyzer/rust-analyzer/blob/master/docs/dev/syntax.md
-
rust-analyzer changelog #134
#12517 (first contribution) fix completion for methods in trait generated by macro.
-
LSP Rust Analyzer keeps telling me `Error NO_RESULT_CALLBACK_FOUND`
-- all the opts to send to nvim-lspconfig -- these override the defaults set by rust-tools.nvim -- see https://github.com/neovim/nvim-lspconfig/blob/master/doc/server_configurations.md#rust_analyzer server = { -- on_attach is a callback called when the language server attachs to the buffer -- on_attach = on_attach, settings = { -- to enable rust-analyzer settings visit: -- https://github.com/rust-analyzer/rust-analyzer/blob/master/docs/user/generated_config.adoc ["rust-analyzer"] = { -- enable clippy on save checkOnSave = { command = "clippy" }, assist = { importGranularity = "module", importPrefix = "self", }, cargo = { loadOutDirsFromCheck = true }, procMacro = { enable = true }, } } },
-
rust-analyzer changelog #130
#12349 publish universal VSIX to make Code happy.
What are some alternatives?
rust-overlay - Pure and reproducible nix overlay of binary distributed rust toolchains
vscode-rust - Rust extension for Visual Studio Code
nixos-flake-example - This is a demo NixOS config, with optional flakes support. Along with notes on why flakes is useful and worth adopting.
Clippy - A bunch of lints to catch common mistakes and improve your Rust code. Book: https://doc.rust-lang.org/clippy/
Nightlies - Nightly builds for DuckieTV
intellij-rust - Rust plugin for the IntelliJ Platform
anyhow - Flexible concrete Error type built on std::error::Error
rustfmt - Format Rust code
nixpkgs - Nix Packages collection & NixOS
eglot - A client for Language Server Protocol servers
nix-cargo-integration - Library to easily and effortlessly integrate Cargo projects with Nix.
rust - Empowering everyone to build reliable and efficient software.