miri
bacon
Our great sponsors
miri | bacon | |
---|---|---|
120 | 25 | |
3,931 | 1,433 | |
2.3% | - | |
10.0 | 7.9 | |
about 13 hours ago | 11 days ago | |
Rust | Rust | |
Apache License 2.0 | GNU Affero General Public License v3.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.
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.
-
Ouroboros is also unsound
You can run miri and it will tell you if the given run triggered any undefined behavior. It will not analyze it for every possible use of the code, but checking for the presence of this specific issue using it should be fairly simple.
-
From Stacks to Trees: A new aliasing model for Rust
If you do encounter a piece of code on which TB performs much worse than SB, do submit it as an issue! There was one recently and we massively improved TB performance on this case by improving garbage collection.
bacon
- Bacon – a background Rust code checker
-
Rust fact vs. fiction: 5 Insights from Google's Rust journey in 2022
Probably one of the biggest speed ups to your inner loop writing / running code is to use something like https://github.com/Canop/bacon/. I used a combination of the docs and GPT chats to increase my learning speed a lot.
-
Project Diagnostics
Nice, I'll have a look. I miss having bacon in a tmux split, wish TS had something like that.
-
Report on platform-compliance for cargo directories
As a macOS user, it boils my brain whenever I've to type in something like ~/Library/Application Support/org.rust-lang.Cargo/config.toml. macOS users have been begging CLI tools to support XDG variables on macOS too. Setting defaults is a strong indication to the community what should be the "preferred" locations. The defaults defined in your article will invariably lead to some authors saying that if that path is good enough for cargo, then it is good enough for their tool. Even the latest draft RFC acknowledges that macOS should use XDG variables too. I've written more about this here.
-
What's your current Vim+Rust setup?
bacon + nvim-bacon
-
What are some useful tools for Rust?
bacon
-
Are there any continuous testing tools with real-time line-by-line IDE feedback for Rust?
I love cargo-watch and still it use it situationally, but as a companion to my editor workflow I mostly switched to bacon. Being able to switch with one keystroke to another cargo subcommand is delightful.
-
What is your number one rust tool?
Try bacon for checks & test!
-
Alternative to watch -cq
Was it bacon perhaps?
- Something similar to Rust's `bacon` tool but for Python?
What are some alternatives?
sanitizers - AddressSanitizer, ThreadSanitizer, MemorySanitizer
rust - Empowering everyone to build reliable and efficient software.
cons-list - Singly-linked list implementation in Rust
cargo-geiger - Detects usage of unsafe Rust in a Rust crate and its dependencies.
helix - A post-modern modal text editor.
Rust-Full-Stack - Rust projects here are easy to use. There are blog posts for them also.
config - configuration.nix is better than dot files
rfcs - RFCs for changes to Rust
darkfi - Anonymous. Uncensored. Sovereign.
nomicon - The Dark Arts of Advanced and Unsafe Rust Programming
rust - Rust for the xtensa architecture. Built in targets for the ESP32 and ESP8266