tokio-uring
coc-rust-analyzer
tokio-uring | coc-rust-analyzer | |
---|---|---|
28 | 16 | |
1,002 | 1,112 | |
2.0% | - | |
4.1 | 8.5 | |
2 months ago | about 23 hours ago | |
Rust | TypeScript | |
MIT License | MIT License |
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.
tokio-uring
- tokio_fs crate
-
Use io_uring for network I/O
While Mio will probably not implement uring in its current design, there's https://github.com/tokio-rs/tokio-uring if you want to use io_uring in Rust.
It's still in development, but the Tokio team seems intent on getting good io_uring support at least!
As the README states, the Rust implementation requires a kernel newer than the one that shipped with Ubuntu 20.04 so I think it'll be a while before we'll see significant development among major libraries.
-
Create a data structure for low latency memory management
That's what the pool is for: https://github.com/tokio-rs/tokio-uring/blob/master/src/buf/fixed/pool.rs
-
Cloudflare Ditches Nginx for In-House, Rust-Written Pingora
Tokio supports io_uring (https://github.com/tokio-rs/tokio-uring), so perhaps when it's mature and battle-tested, it'd be easier to transition to it if Cloudflare aren't using it already.
-
Anyone using io_uring?
- Tokio suffers from a similar problem
-
redb 0.4.0: 2x faster commits with 1PC+C instead of 2PC
Eg via tokio-uring.
-
Efficient way to read multiple files in parallel
I strongly recommend you to look into io-uring and use async executors that take advantages of it: - tokio-uring (not recommended as it is still undergoing development) - monoio - glommio
-
Stacked Futures and why they are impossible
This is my thinking as well. Specifically, I realized that if you don’t use tasks, but rather futures and join, than structured concurrency just works out (at the cost of less efficient poll). In a single-threaded/thread-per-core runtime, tasks could have the same semantics as futures. Somewhat elaborated here: https://github.com/tokio-rs/tokio-uring/issues/81
-
How to use async Rust for non-IO tasks?
There's a new API on Linux called io_uring that has performance benefits, but most executors don't use it yet, except executors meant specifically to harness the power of io_uring like tokio-uring and Glommio
-
Side effects of Tokio
Breaking it down a bit further- Rust's async is zero-cost, and there's no way to write faster equivalent code to the language construct in Rust (and presumably other LLVM languages). Tokio introduces abstractions over OS APIs (indirectly) and provides a runtime. The runtime isn't zero cost, but it is likely to be better optimized for "standard" situations than a homebrewed solution, and its primary competition is in the form of other large async runtimes. On the other hand, Tokio's IO routines are (AFAIK) about as well written as one can get with blocking OS APIs, and the only competitors in that space are projects like tokio-uring that use APIs more well suited for asynchronous usage.
coc-rust-analyzer
-
How to configure vim like an IDE
Rust
-
rust-analyzer while learning
You can absolutely get nvim and rust analyzer working together. I personally use this: https://github.com/fannheyward/coc-rust-analyzer
-
New to Rust. How to setup Nvim as IDE?
nvim plugin](https://github.com/neoclide/coc.nvim) together with the rust analyzer plugin. It's given me the most complete, useful experience developing in rust on nvim. I absolutely love it and can't recommend it enough.
-
Is rust-analyzer necessary?
I use https://github.com/neoclide/coc.nvim with https://github.com/fannheyward/coc-rust-analyzer and this default config: https://github.com/ithinuel/dotfiles/blob/main/.config/nvim/coc-settings.json#L2-L9
-
Coc type annotations in rust
If you're using coc-rust-analyzer, did you try setting rust-analyzer.inlayHints.enable to false?
-
How to include coc extensions with my dotfiles?
Using this plugin I have installed several extensions like coc-clangd and coc-rust-analyzer .
-
Which IDE or Editor you use?
It works pretty well with coc-rust-analyzer actually. but I eventually found the file tree in VSCode very useful, also the debugging interface, so I use VSCode with the Vim plugin. It is the best of both worlds how I feel.
-
vim racer go to function definition
I would install coc.nvim and https://github.com/fannheyward/coc-rust-analyzer
-
Vim - Using clippy as a linter
Yeah sorry I thought you were saying to use the rust-analyzer vim plugin.
-
friendly reminder for our vscode folks, use rust-analyzer
VIM users too! It is available as a language server extension for CoC, called coc-rust-analyzer and it works just as well as the VSCode version.
What are some alternatives?
libuv - Cross-platform asynchronous I/O
rust.vim - Vim configuration for Rust.
glommio - Glommio is a thread-per-core crate that makes writing highly parallel asynchronous applications in a thread-per-core architecture easier for rustaceans.
rust-analyzer - A Rust compiler front-end for IDEs
liburing
rust-analyzer - A Rust compiler front-end for IDEs [Moved to: https://github.com/rust-lang/rust-analyzer]
monoio - Rust async runtime based on io-uring.
neovim-rust - Sample neovim and vim configurations for Rust development
tokio - A runtime for writing reliable asynchronous applications with Rust. Provides I/O, networking, scheduling, timers, ...
tree-sitter - An incremental parsing system for programming tools
diesel_async - Diesel async connection implementation
coc-texlab - TexLab extension for coc.nvim