I feel like removing references from Rust would "solve" a lot of problems. ;)
05.03.2026 18:45
👍 2
🔁 0
💬 1
📌 0
I feel like removing references from Rust would "solve" a lot of problems. ;)
website: choose a password
me: ,p?YG;qtChe?DAh@&o]`zg"k,
website: sorry, not strong enough. needs to contain a number.
Me too!
The schedule including the talk details for RustWeek 2026 is now published!
2026.rustweek.org/schedule/tue...
2026.rustweek.org/schedule/wed...
Which talks are you most excited about? :D
Don't forget to buy your ticket!
A pin button making machine and a few rainbow Rust buttons.
A pile of rainbow Rust pin buttons.
I made another 120 Rust buttons for you all this morning. If you want one, come find me at #RustNationUK on Thursday!
I have bright pink hair now, so should be easy to find.
I am once again sitting in a very fast train to London for #RustNationUK. See you all there!
Catch me on the main stage at RustWeek for the first time! I’ll be speaking on programming languages as a community of belonging, how our perception of what being a programmer has changed over time, and what that means for our communities in the future
After carefully reading and ranking a record number of 185 submissions from 148 speakers, we finally finished the talk selection for RustWeek 2026!
I'm *really* excited about the lineup! Check it out here: 2026.rustweek.org/blog/2026-02...
Don't forget to buy your ticket! See you in Utrecht!
** RustWeek Speakers Announced! **
Check out the selected speakers and talks here:
2026.rustweek.org/blog/2026-02...
Thanks to everyone who submitted to our CFP!
#rust #rustweek2026
The source of the standard Rust Hello World program with the generated assembly before and after the change. The before version has 11 instructions and stores 56 bytes on the stack. The after version has 3 instructions and stores no data on the stack.
🦀 I've improved the implementation behind all the string formatting macros in Rust: println, panic, format, write, log::info, etc. (Everything using format_args!().) They will compile a bit faster, use a bit less memory while compiling, result in smaller binaries, and produce more efficient code! 🎉
Come say hi at #fosdem this weekend!
bsky.app/profile/mara...
Come say hi at #fosdem this weekend!
bsky.app/profile/mara...
Me in a black and white dress with long very pink hair.
Pink!
Jana operating a button making machine, making a batch of Rust buttons.
How many do you think we should make?
A whole pile of pin buttons with the rust logo on top of the progress pride flag.
If you want a Rust button and a discount code for RustWeek, come find me at FOSDEM this weekend!
I now have bright pink hair, so should be easy to find :)
#rustlang #rustweek #fosdem
We might seriously consider that actually! Maybe some sort of "help me move to the Netherlands" desk at the conference or something. Multiple people have already moved to Utrecht and Delft because of RustWeek/RustNL! :D
Only seven hours left to submit your talk proposal for RustWeek 2026!
A snowman made of three big balls of snow. She has leaves as eyes, a carrot as nose, sticks as mouth and arms, and little stones as buttons. She is also wearing my pink winter hat. She looks happy.
☃️
Girls just wanna have fun ✨
sorry for not posting very much lately im hanging out with incredibly attractive women
Perfect! Have fun then. :)
Oh, it's actually quite good.
A pizza with eight mini pizzas on top.
Pizza with extra pizza.
If you want to check the tag bit(s), then something like making .is_aligned() on pointers a const fn would work. (Or a function like .misalignment() -> usize that would give you the sub-alignment bits of a pointer.) Const eval already keeps track of that anyway, so that could be exposed in const.
I do some form of pointer tagging in fmt::Arguments in the standard library, partially in const. Around here: github.com/rust-lang/ru...
But that one works because I can assume that in const eval it's always one specific variant. If you actually need to check the tag bit in const, that's different.
No, but that can be fixed! Was talking about exactly that with Oli recently.
> atomic_compare_Exchange_strong_explicit
oh boy. we're in The Cool Zone of processing shit now
Shoutout to @mara.bsky.social for the Rust Atomics Book. It has prepared me for This Precise Moment.
Yess, do it!
Result::unwrap and Result::expect have the same implementation. There is no difference in allocations or anything like that. result.unwrap() is equivalent to result.expect("called `Result::unwrap()` on an `Err` value").
See doc.rust-lang.org/1.91.0/src/c... and doc.rust-lang.org/1.91.0/src/c...