arya dradjica

From the start of this year, I have slowly been going about designing a query system for Krabby.

I'm ecstatic to announce that, from July 22, I will be paid to work on rustc and Krabby for one day a week.

std::mem::offset_of!

I think it's fairly obvious that I'm a perfectionist.

I have a large backlog of posts to write, but I quickly wanted to share a fun idea I explored on Thursday.

Venting about the state of the world, in the shape of a poem.

To recap: it's November 2025 and I've spent the last two-ish months working on identifier interning.

Last week, I happened to glance at the codebase for rust-analyzer.

Name resolution requires storing lots of identifiers and comparing them to each other very rapidly.

Precisely one year and one week ago, on April 05, 2025, I introduced Krabby.

Krabby appeared on Lobste.rs last week, and I've since received e-mails from people interested in contributing!

I wake up on time to a quiet morning before dawn.

I'm incredibly excited to announce that I'll be giving a talk at RustWeek 2026!

As of yesterday, my website looks a little different.

I've written a work-stealing task queue system for high-performance, CPU-bound applications, called takeaway.

Continuing on from the proof of concept, I'm making good progress on Krabby!

This week has been incredibly productive.

I felt a bit stuck this week.

In my previous post about krabby, I made a "scope tree" data structure with which I performed local name resolution.

I was planning to write a post about the overall architecture I envision for krabby, but there are some complicated bits (regarding macro expansion) that don't feel resolved yet.

A couple of friends got together and, waddaya know, a new programming language project was born.

My online identity comprises a number of accounts spread across dozens of websites and systems.

Daniel J.

Those three words are so hard to say.I remember the first time.

Macros are a very useful feature of the C preprocessor for reducing boilerplate.