#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

🦀 #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)

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

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

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/TodBmsPbbh

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/jfNoMGAkgf

🦀 #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".

🥵

🦀 #Rust Tip #117: fn foo(&self) fn bar (&mut self) fn baz (self) fn boo (mut self) Confused about which one to use in your struct implementations? Here's a useful overview:

Rust's async is beautiful chaos 😮‍💨 Most languages hide concurrency complexity. Rust makes you face it and that's why it's faster. Looks simple - async fn fetch_data() { let result = api_call().await; } But under the hood? Rust compiles this into a state machine.

🦀 #Rust Tip #116: Most of us should know Mutex<> for locking access to specific resources. However, this does also require locking the resources for read. If you need concurrent access to read, take a look at RwLock<> https://t.co/luPgDHcRSk

Note: the reason to_uppercase() returns an iterator is that some characters capitalize to two chars. E.g., "ffi" (Unicode) to "FFI"

🦀 #Rust Tip #115: Here's an interesting self-referential use of iterators, from Rustlings ( https://t.co/qP5zEIFTd0, highly recommended for Rust learners). We get an iterator that capitalizes the char, then use the chain() operator to attach the rest of the string chars.

"Cargo is the most admired cloud development and infrastructure tool" in 2025, says a Stack Overflow study. https://t.co/o6WBpkaEoO

🦀 #Rust Tip #114: A serde tip: #[serde(flatten)] can be used to beautify Json output when serializing. This is useful to improve the handling of enums in particular:

An amazing overview of the core Rust types and traits: https://t.co/Ak9SANexqK

🦀 #Rust Tip #113: https://t.co/BunGWrJlNN is secretly a decent C build system. You can compile wrappers + link C SDKs for Rust wrappers and calling into C code. BTW those println!s are "hidden" build instructions to Cargo. Who needs Makefiles? 🦀

🦀 #Rust Tip #112: Rust will happily compile and call C functions in unsafe mode. Just declare them in an extern "C" block. Great for interop with legacy code or standard library C functions.

🦀 #Rust Tip #111: You can use the examples/ directory in your crate and cargo run --example <name> to run quick experimentations, demos or tests without affecting your https://t.co/OlqnBdRobN file.

🦀 #Rust Tip #110: Rust 2024 edition allows if let Some() chaining. Finally!