Daily Rust

Daily tips & tricks for Rust 🦀 programming.

Following back all accounts with 🦀 or 🐪 in their profile.

[Daily Rust @rustoftheday]

@NeoSmart What is a better alternative?

[Daily Rust @rustoftheday]

Want true pub-sub semantics in Rust?

The Bus crate gives you SP→MC broadcast semantics.

Crossbeam’s MPSC supports multiple consumers, but it round-robins messages, not exactly what you want for fan-out.

https://t.co/RdrhaL31li

[Daily Rust @rustoftheday]

@nother_pleb Agree to using it as a safety net, but not as a primary way of handling errors.

[Daily Rust @rustoftheday]

🦀 #Rust Tip #119:

Some folks suggest using std::panic::catch_unwind as a solution to the recent unwrap() panic that stopped the internet.

In my opinion this is an anti-pattern, some thoughts:
- bypasses memory safety constraints (e.g., panic in unsafe block)

[Daily Rust @rustoftheday]

@_Felipe Great idea if you want to jump straight into undefined behavior. One of the tenets in Rust is to prevent undefined behavior. In the case of unhandled errors (unrwap()) the sound option is to stop execution. There is unwrap_or_default() though...

[Daily Rust @rustoftheday]

#119 (contd.)
- imposes runtime cost by stack walking
- encourages using panic for control flow
- many APIs are not unwind-safe
- cannot catch "fatal" errors such as out-of-memory

[William Saar @saarw]

You generally want a Clippy linter like this one in your Rust production code

[Daily Rust @rustoftheday]

@LundukeJournal We should note it wasn't a memory issue but unsound handling of an error state.

[Daily Rust @rustoftheday]

@deviant_studio @grok They were basically calling a function that either returns a successful result or an error. Production code would normally handle the error case. Calling unwrap() will panic and halt execution if there was an error.

[Daily Rust @rustoftheday]

Don't use unwrap() in your production code, boys and girls! 😃

[Tim McNamara @timClicks]

Cloudflare generated many millions of HTTP 5XX responses today. They were triggered because code in a core proxy called .unwrap() on a Result for an operation that was expected to never fail.

[Daily Rust @rustoftheday]

@ChShersh @jino_rohit the naked pointers burn the eye

[Daily Rust @rustoftheday]

@renzocarbonara are you referring to "fat enums" 🤣😇?

[Daily Rust @rustoftheday]

🦀 #Rust Tip #118:

Result::and_then lets us chain operations that return Result, bypassing nested pattern matching. Although the ? operator often accomplishes the same, and_then allows us to remain in a more functional "combinator style".

[Orhun Parmaksız 👾 @orhundev]

Animate anything with Rust 🦀

🌀 KramaFrame — A simple, generic, and flexible keyframe animation library.

⚡ Manage multiple animations, apply easing functions, and map progress to any range.

🐁 Includes a terminal demo w/ @ratatui_rs

⭐ GitHub: https://t.co/Jqpj1PxPLZ

#rustlang #animation #library #programming #terminal #ratatui #tui

[Daily Rust @rustoftheday]

@yotstack There is a .then() method for async futures in Rust as well, but mostly .await is sufficient.

[Orhun Parmaksız 👾 @orhundev]

This is gold if you're using async Rust 💯

🌀 channels-console — A TUI dashboard for inspecting std/tokio/futures/crossbeam channels.

📊 Watch messages, queue depth, throughput & memory usage live.

🦀 Written in Rust & built with @ratatui_rs

⭐ GitHub: https://t.co/DgetvpBJGI

#rustlang #ratatui #tui #async #concurrency #tokio #debugging

[Daily Rust @rustoftheday]

@ChShersh I see what you are doing 😀Just give in to the urge and switch to #rustlang

[Daily Rust @rustoftheday]

@barettorein @axiosopher Not sure I follow 100%, if statements don't need round parens, for example.

Also, try a C++ closure

auto add = [&sum](int v){ sum += v; };

ampersand and all types of possible parens

Rust:

let mut add = |v| { total += v; };

[Abhimanyu Shekhawat @abshekha]

🥵

[Daily Rust @rustoftheday]

@axiosopher IMHO the killer features of Rust are the high-level abstractions baked in at "Zero Cost", with much better ergonomics (==readability) than equivalent features e.g., in C++. Memory safety is just an additional safeguard the compiler provides.