Ralith

And more to the point, does it have any bearing on structs whose last fields are sized?

Isn't that equally true of normal structs?

Wait, what? I don't see anything like that in the reference.

Ah, I thought ordered fields were required for tuples, but indeed repr(Rust) makes no such requirement.

Is that actually enough? (u8, u16) would need to be at an address that's *one greater than* a multiple of 4.

They don't really solve similar problems, do they?

** Speaker announcement ** Catch Sebastian Sydow's talk 'Writing GPU shaders in plain Rust' at RustWeek 2026!
Info & tickets: 2026.rustweek.org/talks/sebast...

See you in Utrecht May 18-23, 2026!

#rustweek2026 #rustlang

In a very real sense, it's karmic punishment for the rushed adoption of flakes.

At baseline, any pointer structure can be translated into an equivalent structure that uses indexes into a Vec or Slab. Usually this improves locality and makes serialization much easier without any cleverness required.

As soon as you compromise on "it must not suck" as a design goal, the remaining goals don't matter any more.

I think it would be a code smell to do the other thing on purpose, but you could write correct code that did so if you really wanted to, and maybe someone has.

Regardless, I agree that warning by default would make a lot of sense. Not sure how to make that happen, though.

I went a little overboard with this and a little bit insane. moultano.wordpress.com/2026/02/22/t...

"i dont like rust because i dont like fighting the borrow checker" then dont write code the borrow checker doesnt like idiot

zoom, enhance

I feel like this really wants some kind of filtering. Supersampling?

fractal

alacritty has been fine to me lately

I wrote a clippy lint for this: coerce_container_to_any

We are excited to announce that we can successfully use Rust's async/await on the GPU. This has never been done before.

www.vectorware.com/blog/async-a...

Supporting Rust's async/await (and futures) enables existing Rust code to work on the GPU and makes GPU programming more ergonomic.

Just shipped bsky-comments!

Embed Bluesky threads anywhere with a zero-dependency Web Component.

• Framework Agnostic (Native WC)
• < 3kb gzipped
• Zero Config: Just paste the Post URL
• Light DOM: Fully customizable (CSS/Tailwind)

github.com/florianschep...

#webdev #opensource #buildinpublic

fine-grained oauth scopes when authenticating with tangled

quick weekend update: we now have fine-grained oauth scopes!

Me using git in 2024: "it has a few rough edges, sure, but it's really nice!"

Me using git in 2025, having used jj for 2 months: "HOW DO YOU PEOPLE LIFE LIKE THIS?!"

Happy birthday to one of my favourite haters, Charles Darwin

First thoughts on integrating with standard.site Notes on the limitations and unresolved design questions encountered while integrating a blog with standard.site.

First thoughts on integrating with standard.site

swing by the bakery

jj makes version control fun in all the ways git doesn't.

Whoa nice! If you're hesitant to try @jj-vcs.dev because you're a Magit user maybe try this out

A power graph showing a sharp spike, followed by a medium plateau, followed by a very low baseline

A screenshot of the following rust code: let mut red = Output::new(p.P3_18, Level::High, DriveStrength::Normal, SlewRate::Slow); loop { Timer::after_millis(900).await; // For the 100ms the LED is low, we manually take a wakeguard to prevent the // system from returning to deep sleep, which drastically increases our power // usage (experimentally: 1660uA vs the 154uA visible with these clocks *not* // running in deep sleep), but also prevents these clock sources from being // disabled automatically. red.set_low(); let _wg = WakeGuard::new(); Timer::after_millis(100).await; red.set_high(); // The WakeGuard is dropped here before returning to the top of the loop. When this // happens, we will enter deep sleep automatically on our next .await. }

This is the CPU boosting up to 3.25mA current when we wake up from an interrupt and start up some clocks, then chilling out at 1.6mA while I force it into light-sleep, followed by dropping down to 150uA for 900ms as I allow it to go to deep sleep.

All automatically.

github.com/embassy-rs/e...

Living the dream of async Rust!

"Hard for the compiler to reason about" was short-hand for "requires the extra syntax that the question was complaining about, plus additional constraints on your program structure," and trying to convey a subtext that it's worth critically examining assumptions about when they're needed.