Our great sponsors
-
-
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
-
rust-analyzer
Discontinued A Rust compiler front-end for IDEs [Moved to: https://github.com/rust-lang/rust-analyzer] (by rust-analyzer)
-
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
See https://github.com/intellij-rust/intellij-rust/issues/6908 - it contains instruction how to enable procedural macro support for IntelliJ Rust plugin
This used to be a Code bug. I thought it got fixed, but now I see it again.
VS Code, however, doesn’t have a concept of “build” and “build error” at all. This forces us to create “run cargo check on save” contraption on the server side, to shoehorn build errors into “as you type” UX. This conceptually is very wrong — compiler should be invoked and controlled by the editor/user, rather than by the analysis engine. The whole of https://github.com/rust-analyzer/rust-analyzer/tree/master/crates/flycheck should live client-side, except that VS Code literary has no API for this.
https://github.com/davidoguns/dotfiles -- the nvim subfolder obviously but the tmux conf did some quality of life things for fonts and colors. This works beautifully in WSL2 + Windows native. I'm able to same the same config between Windows and Linux with ripgrep, ms build tools and clang in tjhe Windows user path, everything works just the same in Windows and Linux terminal. NerdFonts installed. Treesitter is the wildcard that needs the build tools to compile compatible language parse shared libraries.
https://github.com/LunarVim/Neovim-from-scratch which you can follow along setting up with: https://www.youtube.com/watch?v=ctH-a-1eUME&list=PLhoH5vyxr6Qq41NFL4GvhFp-WLd5xzIzZ