The Missing Piece in Rust Error Handling

This article argues that Rust’s error APIs can preserve concrete error types without forcing each combination into a bespoke enum. It presents an error-set approach, using eros to compose errors from operations while keeping function signatures explicit; the trade-off is an additional library and API pattern to evaluate against existing typed-enum and opaque-error approaches.

The Lobsters page showed no readable comments when checked, despite the front-page snapshot listing five.

• Lobsters discussion

The Missing Piece in Rust Error Handling

This article argues that Rust’s error APIs can preserve concrete error types without forcing each combination into a bespoke enum. It presents an error-set approach, using eros to compose errors from operations while keeping function signatures explicit; the trade-off is an additional library and API pattern to evaluate against existing typed-enum and opaque-error approaches.

The Lobsters page showed no readable comments when checked, despite the front-page snapshot listing five.

• Lobsters discussion

The Async Multiprocessing Has Sound Foundations in Linux, But Further Testing Is Needed

Linux already has the core pieces for asymmetric multiprocessing (AMP), but maintainers need more reviewers, contributors, and repeatable hardware tests to keep them healthy.

Wolfram Sang’s survey follows his effort to upstream a hardware-spinlock driver. It explains how Linux combines remoteproc, RPMsg, mailboxes, shared memory, and SCMI to coordinate application CPUs with real-time cores—and why firmware-specific mailbox arrangements complicate the textbook diagrams. One practical bottleneck is that testing a driver can require modified firmware and U-Boot; OpenAMP’s examples also do not yet run uniformly across supported boards.

InfoQ has no reader-comment section for this article.

This Week in Rust 670

Posted by TWiR Contributors on 2026-09-23 from This Week in Rust