reference
miri
reference | miri | |
---|---|---|
22 | 122 | |
1,140 | 3,973 | |
1.8% | 2.7% | |
8.8 | 10.0 | |
8 days ago | 5 days ago | |
Rust | Rust | |
Apache License 2.0 | 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.
reference
-
Why is there no standard way of removing the mutability property from a reference?
Is perfectly valid Rust code. And there's reborrow, too.
-
Let's thank who have helped us in the Rust Community together!
I truly appreciate how much effort u/ehuss puts into maintaining The Rust Reference, considering that documenting stuff is not usually a fun task people want to do. Not to mention that ehuss is also the Cargo team lead, responsible for developing one of the most loved tools in Rust. ehuss's insightful knowledge always ensures that Cargo works without unexpected surprises.
-
noob question about moving references
Here is (somewhat long) discussion on the topic with other examples: https://github.com/rust-lang/reference/issues/788
-
Announcing Rust 1.66.0
The PR for updating the documentation is here, still under discussion: https://github.com/rust-lang/reference/pull/1055
-
Can someone please explain this to me? How does the compiler know about this for more advanced cases and when does it do this?
thank you this is definitely interesting and i need to read more. For anyone else, this is the thing I found about this issue when I looked it up. It's a github issue about how little documentation there is on the subject and that there should be more. Even the initial post has a lot of interesting details and links. Thanks for bringing it up although sorry it seems your comment went a bit over the heads of some redditors.
-
Anything C can do Rust can do Better
⭐ The Rust Reference - repo
-
GAT section in new version of Rust book?
For the rust reference, there is an open pull request https://github.com/rust-lang/reference/pull/1265/
-
Hey Rustaceans! Got a question? Ask here! (33/2022)!
&mut * is reborrowing which is allowed
-
Why is rust so difficult to learn?
Officialhttps://www.youtube.com/watch?v=rAl-9HwD858&list=PLqbS7AVVErFiWDOAVrPt7aYmnuuOLYvOa The official rust book Rust by example The rust docs Rustlings the most fun way imo
-
PSA - Most Rust tooling runs only on the default feature set and current platform if no special steps are taken
I've opened a PR to add this more prominently to the Conditional Compilation entry in the Rust reference.
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?
rust-by-example - Learn Rust with examples (Live code editor included)
cons-list - Singly-linked list implementation in Rust
mrustc - Alternative rust compiler (re-implementation)
sanitizers - AddressSanitizer, ThreadSanitizer, MemorySanitizer
tour_of_rust - A tour of rust's language features
rust - Empowering everyone to build reliable and efficient software.
stdarch - Rust's standard library vendor-specific APIs and run-time feature detection
Rust-Full-Stack - Rust projects here are easy to use. There are blog posts for them also.
utils - Utility crates used in RustCrypto
rfcs - RFCs for changes to Rust
rust - Rust for the xtensa architecture. Built in targets for the ESP32 and ESP8266
nomicon - The Dark Arts of Advanced and Unsafe Rust Programming