Dion Dokter

Oh cool! Result::flatten is now stabilized :D

Async Rust vs RTOS showdown! - Blog - Tweede golf It's time for another technical blog post about async Rust on embedded. This time we're going to pitch Embassy/Rust against FreeRTOS/C on an STM32F446 microcontroller.

A couple of years ago I wrote this blog post: tweedegolf.nl/en/blog/65/a...

Generally these numbers should still hold up.

I'm also taking the opportunity to miette-ify the codebase and get really awesome error messages in there.

Thanks for the cool work!

Yep! This is really nice. I've been porting my device-driver crate to KDL. It has a field called 'allow-address-overlap' and in other formats you had to specify true even when the default when not present is false.

It's awesome how nicely it sits between data format and dsl

Tom Paris and captain Janeway as lizards from the Voyager episode Threshold.

You don't want to reach warp 10. The captain and the pilot might just procreate with each other

Is it because of the formatting? Are you using core::fmt?

You might be able to get it to:

NETSTACK.log(format_args!("hello: {}", 42)).await;

Not sure if that's better though

crates.io: Rust Package Registry

Just released sequential-storage 5.0.0. Compared to 4.0.0 there are a nice bunch of edge case problems fixed.
It's a barely breaking change, so easy to update!

crates.io/crates/seque...

Idk, could just be sensor differences too. But different enclosures also definitely have impact

Technology | 2025 Stack Overflow Developer Survey

once again, #rustlang is the most admired programming language on the stack overflow survey: survey.stackoverflow.co/2025/technol...

One more thing Those of you interfacing RP2350 to retro computer hardware will be pleased to hear that, after an extensive qualification campaign, RP2350 is now officially 5V tolerant! Just make sure to keep VDDIO powered when 5V is applied to any GPIO pad, otherwise the pad will be damaged. And be sure to read the relevant sections in the updated datasheet.

Also

RP2350 A4, RP2354, and a new Hacking Challenge - Raspberry Pi New A4 stepping of our RP2350 microcontroller now available, with security and other improvements. Plus: another RP2350 Hacking Challenge!

New RP2350 stepping just dropped, E9 fixed.

www.raspberrypi.com/news/rp2350-...

This is more vibes-based than I wanted, but here's the new filtering code for stackdump: github.com/tweedegolf/s...

Now when you run the tool, you don't get spammed with defmt stuff

Apparently it's an optimization: github.com/llvm/llvm-pr...

Dwarf debug info showing a variable with a linkage name and an address

NM output showing that variable doesn't have a symbol, but at the same address is a symbol called .L_MergedGlobals.1067

What the hell are merged globals! And why is it breaking the debug info! 😡

I'm reminded of how much gaslighting elf and dwarf do.

The dwarf claims there's a variable with a certain linkage name.
I then check the elf, and there I can't find it.

So does it exist?
Did LTO remove it without updating the dwarf?

Unless I want to dig into LLVM, there's no way to find out...

SB = stacked borrows
TB = tree borrows

Both proposed formal models for what is considered valid aliasing (i.e. provenance), but neither have been officially adopted and both have slightly different (and sometimes confusing/unintended) behavioral nuances.

Love this explanation! Thanks!

Ha, those are much more technical terms than I'd use (or know), but yes this

Random thought:

`slice.as_ptr()`

is not the same as

`&raw const slice[0]`

with regards to (strict) pointer provenance

Blog - Tweede golf Tech blog on web, security & embedded

We have 100+ Rust-related articles on our blog! Read them here: tweedegolf.nl/en/blog/rust

Topics: web development, systems programming, Embedded Rust, open-source projects, memory-safety, interoperability with other languages, testing and bug hunting.. and much more.

Enjoy!

#rustlang

New blog post: I am a Rust compiler engineer looking for a new job

nnethercote.github.io/2025/07/18/l...

Does anybody know of a tool that can analyze the use (and maybe durations) of critical sections?

I've never done hardcore realtime projects, but sometimes there's a requirement of 'needs to happen in 50ms'. It'd be nice to get more analysis instead of simple testing and gut feeling

I think that's Gource

This looks great!

That could work if literally all formatting needs to be deferred. But that might also break normal code

Public view of rust-lang | Zulip team chat Browse the publicly accessible channels in rust-lang without logging in.

Looking for feedback here: rust-lang.zulipchat.com#narrow/chann...

Oh lol, didn't look through the other replies. I'm not the first mention zmq 😇

ZeroMQ An open-source universal messaging library

Maybe take some inspiration from the ZeroMQ website? zeromq.org

(Though maybe not, because it calls itself 3 different things in the first couple sentences)

But something like 'messaging library' sounds good I think

It might be stupid, but when I open a blog and find out the sentences don't have their first words capitalized, I tend to not read the blog...

GitHub - diondokter/intern-experiment: Could Rust itself do string interning? (and formatting?) Could Rust itself do string interning? (and formatting?) - diondokter/intern-experiment

Link to test project: github.com/diondokter/i...