unsafe-code-guidelines
x11rb
unsafe-code-guidelines | x11rb | |
---|---|---|
74 | 14 | |
640 | 340 | |
1.3% | - | |
6.9 | 8.7 | |
about 2 months ago | 3 days 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.
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.
x11rb
-
My (challenging) experience building a window switcher for Ubuntu
xdotool worked ... but I didn't want to depend on external command-line tools, so I decided to look for X11 bindings for Rust. The best library I could find was x11rb. It had very little documentation and almost no one used it (it was difficult to find people who could help me with it). Fortunately, it had a detailed tutorial. Still, it was a struggle to make things works sometimes.
-
x11rb: Listening to key presses from anywhere on the screen
I'm using x11rb, X11 Rust Bindings. I modified some code from this tutorial so that I'm listening to key presses from parent_win (screen.root) rather than win:
-
Handling two types of errors in the same function
In the end, I decided to use x11rb: https://github.com/psychon/x11rb. This way I don't have to run external commands.
-
Moving a window with Rust X11 bindings
I'm trying to move a window (the GNOME terminal) with x11rb. I followed this tutorial. But the move_window function doesn't move the window.
-
x11rs can't access window created with gtk-rs
I'm using x11rb to interact with a window created with gtk-rs. window_id is the ID of the window created with gtk-rs. window_id_2 is the ID of the window created with x11rb (for testing purposes).
-
Focusing/switching X11 windows with a Rust crate
I also checked x11rb, but I think it's too low level (and too complicated).
-
X11 programming: x11rb or rust-xcb ? What's the difference ?
There is a comparison page in x11rb but it seems to be outdated w.r.t rust-xcb and the unsafe claims, so would appreciate other perspectives.
-
We never know who is delusional..
Do you have a source for that or any specifics on how it "can't handle" the usecases? There's already work in Rust around fully supporting X11 (for example https://github.com/bread-graphics/breadx or https://github.com/psychon/x11rb)
-
Pgwm 0.3 a pure rust `no_std` no libc window manager.
I was thinking about specializing x11rb which is a great library for interfacing with X11, to my specific single threaded use case.
-
I wrote an x11 tiling window manager inspired by DWM that I've been using for a few months now. If you're using x11 and want to try out a new tiling window manager I'd love your feedback!
So if firefox is an application you can find you can query the WM_CLASS property, like this. Other applications might not set that and you'd have to use some other property or information to deduce that this given window(which is just a u32) is actually applicationA. A tip is to start the application, use xprop and see what properties it sets. call_wrapper.rs contains a lot of code about querying different properties. The x11rb example simple_window.rs has a few examples of the other side of that showing how an application can set its on properties.
What are some alternatives?
tokio - A runtime for writing reliable asynchronous applications with Rust. Provides I/O, networking, scheduling, timers, ...
too-many-lists - Learn Rust by writing Entirely Too Many linked lists
rust - Empowering everyone to build reliable and efficient software.
alexandrie - An alternative crate registry, implemented in Rust.
rfcs - RFCs for changes to Rust
minimax-rs - A generic implementation of Negamax in Rust.
bevy - A refreshingly simple data-driven game engine built in Rust
i3status-rust - Very resourcefriendly and feature-rich replacement for i3status, written in pure Rust
miri - An interpreter for Rust's mid-level intermediate representation
nomicon - The Dark Arts of Advanced and Unsafe Rust Programming
pgwm - A minimal tiling x11 window manager