reference
unsafe-code-guidelines
reference | unsafe-code-guidelines | |
---|---|---|
22 | 74 | |
1,140 | 640 | |
1.8% | 1.3% | |
8.8 | 6.9 | |
8 days ago | about 2 months ago | |
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.
unsafe-code-guidelines
-
Passing nothing is surprisingly difficult
Useful context on the Rust side is this issue [1]. It sounds like some of the author's concerns are addressed already.
[1]: https://github.com/rust-lang/unsafe-code-guidelines/issues/4...
-
Blog Post: Non-Send Futures When?
Is this captured by one of the known soundness conflicts? If not then should consider adding it to the list.
- Are crates like vcell and volatile cell still unsound?
-
Question: Are there things for Unsafe Rust learn from Zig?
There are some competing proposals for different memory models. Stacked borrows is the current proposal, but there are more work in the approproate WG.
-
Let's thank who have helped us in the Rust Community together!
Thank you /u/RalfJung for bringing formal methods to Rust, both through models like Stacked Borrows, by developing miri, and by working on unsafe-code-guidelines which aims to specify exactly what is and isn't allowed in unsafe code (surprisingly, it's an open question as 2023!)
- Questions about ownership rule
-
Noob Here: Why doesn't this work?
You could imagine some way to make this safe for example automatically convert &'short &'long mut T to &'short &'short T, but it's non-trivial to prove they are safe at all, not to mention ensuring this is correctly implemented in the compiler. If you're interested there's also a discussion on whether the opposite (& & T to & &mut T) is sound here.
-
When Zig is safer and faster than (unsafe) Rust
Agreed! MIRI is so good, it still feels like magic to me. It also comforts me that the Rust team takes improving unsafe semantics seriously, with the past Unsafe Code Guidelines WG and today's operational semantics team (t-opsem).
-
Safety and Soundness in Rust
I think there are some aspects of this rule that are still undecided. See for example:
- https://github.com/rust-lang/unsafe-code-guidelines/issues/8...
- https://github.com/rust-lang/miri/issues/2732
-
I wanna be a crab.
C is much better specified than unsafe Rust. Some things are just not worked out yet in Rust. This may sometimes even bite very experienced devs, such as this issue with Box's aliasing semantics, which tripped up the author of left-right.
What are some alternatives?
rust-by-example - Learn Rust with examples (Live code editor included)
tokio - A runtime for writing reliable asynchronous applications with Rust. Provides I/O, networking, scheduling, timers, ...
mrustc - Alternative rust compiler (re-implementation)
rust - Empowering everyone to build reliable and efficient software.
tour_of_rust - A tour of rust's language features
rfcs - RFCs for changes to Rust
stdarch - Rust's standard library vendor-specific APIs and run-time feature detection
x11rb - X11 bindings for the rust programming language, similar to xcb being the X11 C bindings
utils - Utility crates used in RustCrypto
bevy - A refreshingly simple data-driven game engine built in Rust
rust - Rust for the xtensa architecture. Built in targets for the ESP32 and ESP8266
miri - An interpreter for Rust's mid-level intermediate representation