#rustanalyzer — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #rustanalyzer, aggregated by home.social.
-
Forcing #Zed to use #beta of the #rust-analyzer for the project is neither trivial nor obvious. It by default calls stable rust-analyzer ignoring rustup's override for the project; on top of that installing rust-analyzer beta using #rustup is non-obvious and doesn't happen automatically with the override to the beta chanel to my disappointment.
Fact #Zed doesn't handle environment variables in settings files doesn't help.
-
Forcing #Zed to use #beta of the #rust-analyzer for the project is neither trivial nor obvious. It by default calls stable rust-analyzer ignoring rustup's override for the project; on top of that installing rust-analyzer beta using #rustup is non-obvious and doesn't happen automatically with the override to the beta chanel to my disappointment.
Fact #Zed doesn't handle environment variables in settings files doesn't help.
-
Forcing #Zed to use #beta of the #rust-analyzer for the project is neither trivial nor obvious. It by default calls stable rust-analyzer ignoring rustup's override for the project; on top of that installing rust-analyzer beta using #rustup is non-obvious and doesn't happen automatically with the override to the beta chanel to my disappointment.
Fact #Zed doesn't handle environment variables in settings files doesn't help.
-
Rust-analyzer has began using CPU in the background. It doesn't do it immediately, but if I leave VSCode open, then I notice that in hour or so, it will start to use 5-10% of CPU just by doing nothing. I have to restart the VSCode to get it to behave.
-
Rust-analyzer has began using CPU in the background. It doesn't do it immediately, but if I leave VSCode open, then I notice that in hour or so, it will start to use 5-10% of CPU just by doing nothing. I have to restart the VSCode to get it to behave.
-
Rust-analyzer has began using CPU in the background. It doesn't do it immediately, but if I leave VSCode open, then I notice that in hour or so, it will start to use 5-10% of CPU just by doing nothing. I have to restart the VSCode to get it to behave.
-
Rust-analyzer has began using CPU in the background. It doesn't do it immediately, but if I leave VSCode open, then I notice that in hour or so, it will start to use 5-10% of CPU just by doing nothing. I have to restart the VSCode to get it to behave.
-
Rust-analyzer has began using CPU in the background. It doesn't do it immediately, but if I leave VSCode open, then I notice that in hour or so, it will start to use 5-10% of CPU just by doing nothing. I have to restart the VSCode to get it to behave.
-
today i discovered the best and probably most useless feature of #rustanalyzer: “view crate graph”
-
today i discovered the best and probably most useless feature of #rustanalyzer: “view crate graph”
-
today i discovered the best and probably most useless feature of #rustanalyzer: “view crate graph”
-
today i discovered the best and probably most useless feature of #rustanalyzer: “view crate graph”
-
today i discovered the best and probably most useless feature of #rustanalyzer: “view crate graph”
-
The unsynn! macro turns out to become a #rustanalyzer stress test 🤔 #rustlang
The code is fine, compiles as intended. R-A doesn't agree.
-
@counterVariable
5. Notice line no(s). 14, 15, 16. If you use `nvim-navic` or `barbecue` for winbar then don't need to tinker it. Otherwise you can remove it.
6. `codelldb` for rust, is recommended if you use debugger and have a setup.#neovim #rust #rustaceanvim #rustanalyzer #dap #codelldb #lazy #mason
-
@counterVariable
5. Notice line no(s). 14, 15, 16. If you use `nvim-navic` or `barbecue` for winbar then don't need to tinker it. Otherwise you can remove it.
6. `codelldb` for rust, is recommended if you use debugger and have a setup.#neovim #rust #rustaceanvim #rustanalyzer #dap #codelldb #lazy #mason
-
@counterVariable
5. Notice line no(s). 14, 15, 16. If you use `nvim-navic` or `barbecue` for winbar then don't need to tinker it. Otherwise you can remove it.
6. `codelldb` for rust, is recommended if you use debugger and have a setup.#neovim #rust #rustaceanvim #rustanalyzer #dap #codelldb #lazy #mason
-
@counterVariable
5. Notice line no(s). 14, 15, 16. If you use `nvim-navic` or `barbecue` for winbar then don't need to tinker it. Otherwise you can remove it.
6. `codelldb` for rust, is recommended if you use debugger and have a setup.#neovim #rust #rustaceanvim #rustanalyzer #dap #codelldb #lazy #mason
-
@counterVariable
5. Notice line no(s). 14, 15, 16. If you use `nvim-navic` or `barbecue` for winbar then don't need to tinker it. Otherwise you can remove it.
6. `codelldb` for rust, is recommended if you use debugger and have a setup.#neovim #rust #rustaceanvim #rustanalyzer #dap #codelldb #lazy #mason
-
@counterVariable
3. Do not setup LSP with rust-analyzer beforehand, rustaceanvim will do it for you.
4. Look at line no. 5, since, you probably didn't/haven't setup any `settings.lua` file to manage macro Neovim settings. Replace the line with `enabled = package.loaded["rust-analyzer"] ~= nil`. This way rustaceanvim will only work when rust-analyzer is available. If you don't care about it remove line no. 5 completely....
#neovim #rust #rustaceanvim #rustanalyzer #dap #codelldb #lazy #mason
-
@counterVariable
3. Do not setup LSP with rust-analyzer beforehand, rustaceanvim will do it for you.
4. Look at line no. 5, since, you probably didn't/haven't setup any `settings.lua` file to manage macro Neovim settings. Replace the line with `enabled = package.loaded["rust-analyzer"] ~= nil`. This way rustaceanvim will only work when rust-analyzer is available. If you don't care about it remove line no. 5 completely....
#neovim #rust #rustaceanvim #rustanalyzer #dap #codelldb #lazy #mason
-
@counterVariable
3. Do not setup LSP with rust-analyzer beforehand, rustaceanvim will do it for you.
4. Look at line no. 5, since, you probably didn't/haven't setup any `settings.lua` file to manage macro Neovim settings. Replace the line with `enabled = package.loaded["rust-analyzer"] ~= nil`. This way rustaceanvim will only work when rust-analyzer is available. If you don't care about it remove line no. 5 completely....
#neovim #rust #rustaceanvim #rustanalyzer #dap #codelldb #lazy #mason
-
@counterVariable
3. Do not setup LSP with rust-analyzer beforehand, rustaceanvim will do it for you.
4. Look at line no. 5, since, you probably didn't/haven't setup any `settings.lua` file to manage macro Neovim settings. Replace the line with `enabled = package.loaded["rust-analyzer"] ~= nil`. This way rustaceanvim will only work when rust-analyzer is available. If you don't care about it remove line no. 5 completely....
#neovim #rust #rustaceanvim #rustanalyzer #dap #codelldb #lazy #mason
-
@counterVariable
3. Do not setup LSP with rust-analyzer beforehand, rustaceanvim will do it for you.
4. Look at line no. 5, since, you probably didn't/haven't setup any `settings.lua` file to manage macro Neovim settings. Replace the line with `enabled = package.loaded["rust-analyzer"] ~= nil`. This way rustaceanvim will only work when rust-analyzer is available. If you don't care about it remove line no. 5 completely....
#neovim #rust #rustaceanvim #rustanalyzer #dap #codelldb #lazy #mason
-
@counterVariable Yea, I have something that works.
NOTE : I've made few assumptions :
1. You use Lazy as package manager.
2. You use Mason.There are few things that you need to keep in mind :
1. My path for this file in my config is -> `lua/plugins/intellisense/languages/rust.lua`. But you can put this file anywhere within the `plugins` directory.
2. You need rust-analyzer for rustaceanvim to work....
#neovim #rust #rustaceanvim #dap #rustanalyzer #codelldb #lazy #mason
-
@counterVariable Yea, I have something that works.
NOTE : I've made few assumptions :
1. You use Lazy as package manager.
2. You use Mason.There are few things that you need to keep in mind :
1. My path for this file in my config is -> `lua/plugins/intellisense/languages/rust.lua`. But you can put this file anywhere within the `plugins` directory.
2. You need rust-analyzer for rustaceanvim to work....
#neovim #rust #rustaceanvim #dap #rustanalyzer #codelldb #lazy #mason
-
@counterVariable Yea, I have something that works.
NOTE : I've made few assumptions :
1. You use Lazy as package manager.
2. You use Mason.There are few things that you need to keep in mind :
1. My path for this file in my config is -> `lua/plugins/intellisense/languages/rust.lua`. But you can put this file anywhere within the `plugins` directory.
2. You need rust-analyzer for rustaceanvim to work....
#neovim #rust #rustaceanvim #dap #rustanalyzer #codelldb #lazy #mason
-
@counterVariable Yea, I have something that works.
NOTE : I've made few assumptions :
1. You use Lazy as package manager.
2. You use Mason.There are few things that you need to keep in mind :
1. My path for this file in my config is -> `lua/plugins/intellisense/languages/rust.lua`. But you can put this file anywhere within the `plugins` directory.
2. You need rust-analyzer for rustaceanvim to work....
#neovim #rust #rustaceanvim #dap #rustanalyzer #codelldb #lazy #mason
-
@counterVariable Yea, I have something that works.
NOTE : I've made few assumptions :
1. You use Lazy as package manager.
2. You use Mason.There are few things that you need to keep in mind :
1. My path for this file in my config is -> `lua/plugins/intellisense/languages/rust.lua`. But you can put this file anywhere within the `plugins` directory.
2. You need rust-analyzer for rustaceanvim to work....
#neovim #rust #rustaceanvim #dap #rustanalyzer #codelldb #lazy #mason
-
@stevenaleach Hey 👋. Do you have any guide on how to start with #rust ?
-
@stevenaleach Hey 👋. Do you have any guide on how to start with #rust ?
-
@stevenaleach Hey 👋. Do you have any guide on how to start with #rust ?
-
@stevenaleach Hey 👋. Do you have any guide on how to start with #rust ?
-
@stevenaleach Hey 👋. Do you have any guide on how to start with #rust ?
-
Finally i got #Embassy working on my #ESP32c6 in #NixOS. By now it should be over 95% reproducible. The last parts have to wait until i finished my day job.
The litte bugger now runs #EmbeddedRust #RustLang.I will share the flake, which is mostly the oxilica/rust-overlay flake with the corrected toolchain and stuff like #RustAnalyzer and `cargo espflash`.
-
Finally i got #Embassy working on my #ESP32c6 in #NixOS. By now it should be over 95% reproducible. The last parts have to wait until i finished my day job.
The litte bugger now runs #EmbeddedRust #RustLang.I will share the flake, which is mostly the oxilica/rust-overlay flake with the corrected toolchain and stuff like #RustAnalyzer and `cargo espflash`.
-
Finally i got #Embassy working on my #ESP32c6 in #NixOS. By now it should be over 95% reproducible. The last parts have to wait until i finished my day job.
The litte bugger now runs #EmbeddedRust #RustLang.I will share the flake, which is mostly the oxilica/rust-overlay flake with the corrected toolchain and stuff like #RustAnalyzer and `cargo espflash`.
-
Finally i got #Embassy working on my #ESP32c6 in #NixOS. By now it should be over 95% reproducible. The last parts have to wait until i finished my day job.
The litte bugger now runs #EmbeddedRust #RustLang.I will share the flake, which is mostly the oxilica/rust-overlay flake with the corrected toolchain and stuff like #RustAnalyzer and `cargo espflash`.
-
Finally i got #Embassy working on my #ESP32c6 in #NixOS. By now it should be over 95% reproducible. The last parts have to wait until i finished my day job.
The litte bugger now runs #EmbeddedRust #RustLang.I will share the flake, which is mostly the oxilica/rust-overlay flake with the corrected toolchain and stuff like #RustAnalyzer and `cargo espflash`.
-
Ever wondered why the language server #RustAnalyzer isn't showing all errors, warnings and lints? 😕
This is especially an issue in #Rustlings where Rust-Analyzer only shows the diagnostics in some of the exercises.
Turns out, Rust-Analyzer uses `cargo check` under the hood which itself stops checking early unless you specify the `--keep-going` flag 🏃🏼
This is fixed in Rust-Analyzer now 😃
https://github.com/rust-lang/rust-analyzer/pull/17561
Thanks to @veykril 🤗
