kanal
miri
kanal | miri | |
---|---|---|
7 | 122 | |
1,253 | 3,973 | |
- | 2.7% | |
5.4 | 10.0 | |
3 days ago | 1 day ago | |
Rust | Rust | |
MIT License | Apache License 2.0 |
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.
kanal
-
I've incidentally created one of the fastest bounded MPSC queue
How does it compare to kanal?
- GitHub - fereidani/kanal: The fast sync and async channel that Rust deserves
-
Which async channel is best?
kanal is a quite recent crate with outstanding performance characteristics. Though it is still quite new. tokio is also very good.
- Kanal: Channels 80x faster than the standard library!
-
Fast sync and async channel, to bring the best of both worlds together.
Thanks both of you, I fixed it with this commit: https://github.com/fereidani/kanal/commit/8a4df536c5723acce491f34a3b1014d00e407187
miri
-
Rust: Box Is a Unique Type
>While we are many missing language features away from this being the case, the noalias case is also magic descended upon box itself, with no user code ever having access to it.
I'm not sure why the author thinks there's magic behind Box. Box is not a special case of `noalias`. Run this snippet with miri and you'll see the same issue: https://play.rust-lang.org/?version=stable&mode=debug&editio...
`Box` _does_ have an expectation that its inner pointer is not aliased to another Box (even if used for readonly operations). See: https://github.com/rust-lang/miri/issues/1800#issuecomment-8...)
-
Bytecode VMs in Surprising Places
Miri [0] is an interpreter for the mid-level intermediate representation (MIR) generated by the Rust compiler. MIR is input for more processing steps of the compiler. However miri also runs MIR directly. This means miri is a VM. Of course it's not a bytecode VM, because MIR is not a bytecode AFAIK. I still think that miri is a interesting example.
And why does miri exist?
It is a lot slower. However it can check for some undefined behavior.
[0]: https://github.com/rust-lang/miri
-
RFC: Rust Has Provenance
Provenance is a dynamic property of pointer values. The actual underlying rules that a program must follow, even when using raw pointers and `unsafe`, are written in terms of provenance. Miri (https://github.com/rust-lang/miri) represents provenance as an actual value stored alongside each pointer's address, so it can check for violations of these rules.
Lifetimes are a static approximation of provenance. They are erased after being validated by the borrow checker, and do not exist in Miri or have any impact on what transformations the optimizer may perform. In other words, the provenance rules allow a superset of what the borrow checker allows.
- Mir: Strongly typed IR to implement fast and lightweight interpreters and JITs
-
Running rustc in a browser
There has been discussion of doing this with MIRI, which would be easier than all of rustc.
-
Piecemeal dropping of struct members causes UB? (Miri)
This issue has been fixed: https://github.com/rust-lang/miri/issues/2964
- Erroneous UB Error with Miri?
-
I've incidentally created one of the fastest bounded MPSC queue
Actually, I've done more advanced tests with MIRI (see https://github.com/rust-lang/miri/issues/2920 for example) which allowed me to fix some issues. I've also made the code compatible with loom, but I didn't found the time yet to write and execute loom tests. That's on the TODO-list, and I need to track it with an issue too.
-
Interested in "secure programming languages", both theory and practice but mostly practice, where do I start?
He is one of the big brains behind Miri, which is a interpreter that runs on the MIR (compiler representation between human code and asm/machine code) and detects undefined behavior. Super useful tool for language safety, pretty interesting on its own.
-
Formal verification for unsafe code?
I would also run your tests in Miri (https://github.com/rust-lang/miri) to try to cover more bases.
What are some alternatives?
unsafe-code-guidelines - Forum for discussion about what unsafe code can and can't do
cons-list - Singly-linked list implementation in Rust
rust-channel-benchmarks - rust channel benchmarks to keep stat of performance of Kanal library in comparison with other competitors.
sanitizers - AddressSanitizer, ThreadSanitizer, MemorySanitizer
ScyllaDB Async Rust Driver - Async CQL driver for Rust, optimized for ScyllaDB
rust - Empowering everyone to build reliable and efficient software.
crossbeam - Tools for concurrent programming in Rust
Rust-Full-Stack - Rust projects here are easy to use. There are blog posts for them also.
rfcs - RFCs for changes to Rust
loole - A safe sync/async multi-producer, multi-consumer channel
nomicon - The Dark Arts of Advanced and Unsafe Rust Programming