
I just ran
```
cargo --version
```
and
```
rustc --version
```
to confirm I have the newest version
Thanks rust-team!
I just ran
```
cargo --version
```
and
```
rustc --version
```
to confirm I have the newest version
Thanks rust-team!
Just noticed a super-cool feature of the #rust language server. I can click on one of the ||s in:
key.contains('.') || key == "debug" || key == "enabled_events" || key == "retries"
then select Apply De Morgan's Law, and it automatically changes to:
!(!key.contains('.') && key != "debug" && key != "enabled_events" && key != "retries")
It's kinda cool to see something I've worked on to be in Debian's archives! It's the #microformats library for Rust. It does force me to be on top of things (which I don't mind). I need to add more examples of use for folks, so this is a bit of an ask to #Rust developers and users (though languages like #JavaScript and #Ruby could benefit too): what kind of examples of use would you want to see from https://microformats.io?
Rust 1.86.0 was released on Thursday! 3 of our engineers have contributed to this release:
bjorn3 / @bjorn3
Folkert de Vries
David Venhoek
Check out the release notes here: https://blog.rust-lang.org/2025/04/03/Rust-1.86.0.html
Just added new methods in the proc-macro
library on the Literal
type:
str_value
cstr_value
byte_str_value
Hopefully it should help to unescape literals when manipulating proc-macro tokens. No need to do it in external crates anymore.
Please help me : I've seen not too long ago a blog post about type oriented programming in #rust #rustlang but I can't find it in my browser history . Can't remember if it was new or a repost, neither if I saw it here or on reddit ... ( if you have nice introductory articles on this subject keep them flowing even if they are not the one I'm looking for)
OK, first pass at a working tiling window manager for OSX is a thing (yes, you read that correctly)
This is me updating Penrose to remove the X11-isms and then implementing a backend for OSX that lets you drop in pretty much all of the existing functionality from the Penrose crate (minus the status bar and a couple of extensions).
It's still pretty hacky at this stage, and there are plenty of bugs to sort out but I'm happy with how much ends up working out of the box!
https://github.com/sminez/penrose/pull/321
https://github.com/sminez/penrosx
Help us create a vision for Rust's future - Jack Huey (Vision Doc Team):
https://blog.rust-lang.org/2025/04/04/vision-doc-survey.html
"Rust turns 10 this year. It's a good time to step back and assess where we are at and [...] where we should be going. Where is Rust succeeding at empowering everyone to build reliable, efficient software [...]? Where are there opportunities to do better? [...] We have taken on the goal of authoring a #Rust Vision RFC [..] for review at the upcoming Rust All Hands."
Sunday Live Stream: Making an AVIF Image Maker for my Static Site Generator in #rust
stop by, say hi
Sigh, I think I might have to switch away from #VisusalStudioCode. Seems the only stuff they work on is #AI, to the detriment of everything else.
Shall I move back to #vim? Or rather #neovim. Do I still have the patience to configure that just the way I like it?
I could also try out that newfangled #zed editor that is getting all the hype these days.
One must-have feature is it having good vim keybindings though, I'm lost without them.
#SoftwareDevelopment #golang #rustlang #rust
This week, I was writing #Rust code to parse the From: line in an email. I wanted to use a library, because email header parsing is notoriously difficult to get right. This library clearly was built expecting multiple addresses to be given on the From: line.
"What nonsense is this?"" I thought. And went to the RFCs, and sure enough, that's supported in RFC822, RFC2822, and RFC5322.
And then 2 days later I found a use for it. And it seems to work.
Firing up the live stream for a bit. Working on my static site generator. #rust
I updated my blog post to link to the daft PR it inspired #rust #rustlang https://schneems.com/2025/03/26/a-daft-procmacro-trick-how-to-emit-partialcode-errors/
I’m interested in seeing Fedi’s opinion on this. Also reply with a more detailed opinion and your language of choice if you feel so inclined. Boost if you are interested in this too.
When my compiler reports an error, I most often see this as:
Hey #rust #rustlang folks... How do I git-depend on a crate in a workspace?
I try to depend on `cloudmqtt-core` from https://github.com/TheNeikos/cloudmqtt but cargo fails with `error: no matching package named `cloudmqtt-core` found`.
Ferron – a fast, memory-safe web server written in Rust
Link: https://github.com/ferronweb/ferron
Discussion: https://news.ycombinator.com/item?id=43555249
Big bugfix release!
pict-rs 0.5.17-pre.11
once again it is not 0.5.17
but i'm getting tempted to just rename it and call it done
https://git.asonix.dog/asonix/pict-rs/releases/tag/v0.5.17-pre.11
Hmmm, according to the #Phoronix comments, #Rust #Rustlang is both woke and fascist ...
At least they red-flag themselves so quickly that it doesn't take me long to decide they belong on my block/ignore list
It's a shame, that every new reader of the Phoronix comments is subjected to loads of toxic rubbish