Search posts, papers, and topics
The post introduces the problem of cyclic trait implementations in Rust, showing how allowing certain cycles could enable “perfect derive” that derives traits based on field types rather than generic bounds. It also explains why naïvely accepting any cycle is unsound, especially with supertraits, and outlines the need for a principled solution.
Codename One reduced startup latency and JavaScript overhead by publishing screen state atomically, indexing style lookups, avoiding unnecessary artwork generation, and refining suspension analysis, yielding measurable speedups.
This Week in Rust #669 is a curated roundup of community newsletters, project/tooling releases, blog posts, walkthroughs, research, the crate of the week, testing calls, and a detailed list of merged PRs across the Rust compiler, standard library, Cargo, rustfmt, Clippy, and rust‑analyzer, plus a brief compiler‑performance triage summary. No new RFCs were approved.
This issue of *This Week in Rust* (Sept 9 2026) aggregates community news, recent Rust releases, notable blog posts, a “crate of the week” (tokio‑rcu), and a long list of merged PRs across the compiler, std, Cargo, rustdoc, rustfmt, Clippy and rust‑analyzer. The most concrete technical highlight is the tokio‑rcu crate, an async‑aware userspace RCU implementation built on Tokio.
This issue of *This Week in Rust* (2026‑08‑26) aggregates community news: official Rust announcements (maintainers‑in‑residence, next‑gen trait solver, supply‑chain attack on arrayref, function‑overloading experiment), a Mozilla JPEG‑XL tooling update, several observations (AI‑assisted C/C++ rewrites, enum‑to‑word speedup, compilation metadata shaving, driver state handling, async vs sync for a r…