Our great sponsors
-
rust-analyzer
Discontinued A Rust compiler front-end for IDEs [Moved to: https://github.com/rust-lang/rust-analyzer] (by rust-analyzer)
-
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.
-
sqlx
🧰 The Rust SQL Toolkit. An async, pure Rust SQL crate featuring compile-time checked queries without a DSL. Supports PostgreSQL, MySQL, and SQLite. (by launchbadge)
-
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.
-
coc.nvim
Nodejs extension host for vim & neovim, load extensions like VSCode and host language servers.
Rust completion generally uses the Language Server protocol through rust-analyzer. There are several language server plugins available for neovim, I'm not entirely sure how much exists for standard vim.
You should take a look at the rustlings exercises and see whether they would be useful for you: https://github.com/rust-lang/rustlings
https://github.com/rust-lang/flate2-rs ?
https://github.com/launchbadge/sqlx ?
For anyone interested, here is a branch with the broken code: https://github.com/doup/sdf_2d/blob/feature/egui/src/main.rs#L422
You'd use it whenever you need to do low-overhead asynchronous IO. The first "motivation" paragraph of the tokio-uring design proposal has a brief overview of the benefits of io_uring. In general, as an application developer, you're unlikely to need to use it directly - if you were writing a webserver or something else that needs to a bajillion concurrent connections, you might use an abstraction built on io_uring (like tokio-uring).
There is https://github.com/tvallotton/rocket_auth, which salts by default IIRC
I use pathogen. I installed rust.vim per https://github.com/rust-lang/rust.vim.
I use neovim, but coc and coc-rust-analyzer support mainline vim as well.
I use neovim, but coc and coc-rust-analyzer support mainline vim as well.
As mentioned by /u/llogiq, std::process::Command will work if you mean shelling out to another binary, but I wanted to point out the crate duct which makes this kind of thing simpler to handle.
I can't find documentation. The Unstable Book has zilch. An older post here says to read aturon's blog post, which is pretty opaque for someone not steeped in type theory, and the PR, which does have usage examples by way of tests, but they're mostly about what is not allowed and only have shorthand comments.