Rust tips<p>The next release of <a href="https://mas.to/tags/RustLang" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>RustLang</span></a> will start warning about "mismatched lifetime syntaxes".</p><p>You can already automatically fix many of these cases by applying an auto-fix for the `elided_lifetimes_in_paths` warning:</p><p> RUSTFLAGS="-Welided_lifetimes_in_paths" cargo fix --all --all-targets</p>
Administered by:
#rustlang
78 posts59 participants0 posts today
RustWasm to Be Archived 
Today’s Issue: There Is No Memory Safety Without Thread Safety, Vivo’s BlueOS Kernel, and Footguns of the Rust WebAssembly Target
open.substack.comRustWasm to Be Archived 🦀Today’s Issue: There Is No Memory Safety Without Thread Safety, Vivo’s BlueOS Kernel, and Footguns of the Rust WebAssembly Target
Awesome links of last week
Check thread below 
What are you doing during a rainy weekend? Instructing CoPilot in #VScode to implement a fully working Blockchain implementation in Rust - with a TUI and WASM-based frontend. I haven't written any line of code, just prompted CoPilot in the right direction. In sum I have spent less than 4 hours on this. I learned a lot about CoPilot, Generative AI, cryptography, and the blockchain technology itself. #GenAI #rust #rustlang #ratatui #wasm #blockchain #crypto #crytography
Ok I'm tired... In #ratatui How Am I supposed to return a Span<'_> from a function ? Where does this lifetime comes from? #rustlang
everything is owned in my function:
fn display_battery_level(bat: f32) -> Span<'_> {
let bat_s = bat.to_string();
match bat {
_ if bat > 50.0 => bat_s.green(),
_ if bat > 25.0 => bat_s.yellow(),
_ => bat_s.red(),
}
}
Red Hat Has Been Rewriting Bash-Based Greenboot in Rust
www.phoronix.comRed Hat Has Been Rewriting Bash-Based Greenboot In RustGreenboot is a generic health check framework for systemd on RPM-OSTree based Linux distributions
Dude. It's been a year since I wrote #rustlang code and I feel like I've forgotten the entire language 
Replied in thread
@kloetzl You can use a concept called "Borrow Splitting" in combination with scoped threads.
This way, your slices that your threads operate on, can have a lifetime shorter than 'static and you don't need to use #unsafe shenanigans. 
Please see this playground with comments on how to do this:
https://play.rust-lang.org/?version=stable&mode=debug&edition=2024&gist=6b028d5bab84d739d34d76d66a750578
On Borrrow Splitting:
https://doc.rust-lang.org/nomicon/borrow-splitting.html
On scoped threads API:
https://doc.rust-lang.org/std/thread/fn.scope.html
play.rust-lang.orgRust PlaygroundA browser interface to the Rust compiler to experiment with the language
In rust, if the macro expansion failed, you get a lot of errors related to the missing macro expansion, which is just noise basically.
I implemented in https://github.com/rust-lang/rust/pull/144409 a check to stop compilation if a macro expansion failed, greatly reducing the number of noisy errors.
Enjoy!
GitHubStop compilation early if macro expansion failed by GuillaumeGomez · Pull Request #144409 · rust-lang/rust
The latest issue of @thisweekinrust is out. We have included 3 issues in the “Call for Participation” section. If you are a Rust developer and want to help fix some issues in our project then please check them out.
These blog posts is a great way to learn about what is going on in the Rust world so definitely worth a read in general.
https://this-week-in-rust.org/blog/2025/07/23/this-week-in-rust-609/
this-week-in-rust.orgThis Week in Rust 609 · This Week in Rust