Just added new methods in the proc-macro library on the Literal type:
str_valuecstr_valuebyte_str_valueHopefully 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)
Password auth in Rust, from scratch - Attacks and best practices
https://lpalmieri.com/posts/password-authentication-in-rust/
Sunday Live Stream: Making an AVIF Image Maker for my Static Site Generator in #rust
stop by, say hi
https://www.europesays.com/de/11209/ Songs gegen rechts kommen nicht ins Radio #BAP #DeutschePresseAgentur #Deutschland #Entertainment #Germany #RadioRegenbogen #Rust #Unterhaltung #WolfgangNiedecken
Pitfalls of Safe Rust
Link: https://corrode.dev/blog/pitfalls-of-safe-rust/
Discussion: https://news.ycombinator.com/item?id=43585742
Spicy take:
Panics aren’t bugs, people are just conditioned to fear stack traces.
Just released: Findutils 0.8.0!
This update brings new formatting options (-fprint0, -fprintf), improved file handling with -files0-from, and more efficient command execution with exec[dir]+.
Now with 80.87% GNU test suite compatibility - our best yet!
Download: https://github.com/uutils/findutils/releases/tag/0.8.0
Show HN: I built a Rust crate for running unsafe code safely
Link: https://github.com/brannondorsey/mem-isolate
Discussion: https://news.ycombinator.com/item?id=43601301
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
rauthy: OpenID Connect Single Sign-On Identity & Access Management https://lobste.rs/s/p814ia #rust
https://github.com/sebadob/rauthy
What a balanced universe:
I found and fixed two bugs today within minutes of one another - one was in #Rust.
I had a "return" where I wanted to "continue" and my service kept dying when I poked it in a certain way.
Then I returned to the irritating bug in the #Python library I was working on. It was touring infinity the long way 'round. It turned out I'd put a "continue" where I should have put a "return".
That was at 36+ hours awake, and felt rather amusing.
⅀"
🖧
".
Not sure if it's really newsworthy, but I'm making progress on my rust/Vulkan game engine.
Here the Sponza scene loaded from a gltf file, with some PBR lighting straight from https://learnopengl.com
1/ Status: of late, I've been learning to write async functional #rust . I do this with every programming language I encounter: try to build a little project, a record of what I learned and how I learned it.
It's served as an insulator from these trying times. I have something to do, something to accomplish, so many things to learn.
Something to distract me.
Every day just gets weirder. I'm hardly alone in fearing for my Social Security, or running afoul of Trump's Stasi.
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.
Rust project's official account will no longer be active on X
