rust-ffi-omnibus
unsafe-code-guidelines
rust-ffi-omnibus | unsafe-code-guidelines | |
---|---|---|
1 | 74 | |
487 | 641 | |
- | 1.4% | |
0.0 | 6.9 | |
over 1 year ago | about 2 months ago | |
SCSS | ||
GNU General Public License v3.0 or later | 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.
rust-ffi-omnibus
-
Hey Rustaceans! Got an easy question? Ask here (9/2021)!
The Rust FFI Omnibus didn't have any examples of this nor have I found anything on SO yet: what's the right way to FFI pass a C# byte[] back and forth as a Rust Vec?
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?
tokio - A runtime for writing reliable asynchronous applications with Rust. Provides I/O, networking, scheduling, timers, ...
alexandrie - An alternative crate registry, implemented in Rust.
rust - Empowering everyone to build reliable and efficient software.
erased-serde - Type-erased Serialize, Serializer and Deserializer traits
rfcs - RFCs for changes to Rust
tail - My implementation of the tail tool to (continuously) read the tail end of a file. See https://en.wikipedia.org/wiki/Tail_(Unix)
x11rb - X11 bindings for the rust programming language, similar to xcb being the X11 C bindings
serde - Serialization framework for Rust
bevy - A refreshingly simple data-driven game engine built in Rust
miri - An interpreter for Rust's mid-level intermediate representation