Email or username:

Password:

Forgot your password?
Mara's posts Post Back to profile
Mara

🦀 I'm really excited about today's #rustlang release! 🥳

- offset_of!
- c"" string literals!
- stripping release binaries by default!
- IP/socket types available in no_std!
- File::create_new (won't overwrite existing files)!
- more array and slice methods (each_ref, chunk methods)!
- Mutex::clear_poison!

blog.rust-lang.org/2024/03/21/

21 March at 13:53 | Open on hachyderm.io
15 comments
fasterthanlime 🌌
Daniel Collin 🦀

@Mara The C-string literals is a nice feature for someone (like me) that has to deal with C style interfaces quite a bit :)

21 March at 13:56 | Open on mastodon.gamedev.place
Snowy :green_junimo:
@Mara I've been looking forward to most of them :neocat_aww:.
Rust is amazing
21 March at 14:01 | Open on junimo.party
Mara

Really cool to see the c"" string literal feature stabilized. I wrote the RFC for c"" string literals [1], so I'm very excited to see it reach stable Rust today.

I had nothing to do with its implementation, however. The implementation was done by @beef [2] and quite a few others worked on it too [3]. Thanks all, for making this happen!

[1]: github.com/rust-lang/rfcs/pull
[2]: github.com/rust-lang/rust/pull
[3]: github.com/rust-lang/rust/issu

Really cool to see the c"" string literal feature stabilized. I wrote the RFC for c"" string literals [1], so I'm very excited to see it reach stable Rust today.

I had nothing to do with its implementation, however. The implementation was done by @beef [2] and quite a few others worked on it too [3]. Thanks all, for making this happen!

21 March at 14:05 | Open on hachyderm.io
Mo :ferris: :tux:

@Mara clear_poison is huge! 🚀

21 March at 14:11 | Open on fosstodon.org
Mara
Mo :ferris: :tux:

@Mara Not directly, but I looked for something like this once to avoid a panic. In that case, I just wanted to "repair" the value inside by resetting it to some initial value.

21 March at 14:35 | Open on fosstodon.org
chrysn

@Mara That poison clearing needed a lot of mental gymnastics to see why this is not unsafe.
I'd describe it as "Mutex users already have to make sure to always have their &mut T usable, or at least have to fix that during unwinding, and if the mutex is poisoned, that means that the thread that poisoned it unwound". Does that sound about right?

21 March at 14:37 | Open on chaos.social
Mara

@chrysn Yes, poisoning isn't needed for soundness. No type should cause unsoundness because of unwinding. It's the same reason that AssertUnwindSafe is not unsafe. (The "safe" in "AssertUnwindSafe" is confusing, but it's unrelated to Rust's normal concept of memory (un)safety.)

21 March at 14:42 | Open on hachyderm.io
[object Object]
@chrysn @Mara you could already retrieve the poisoned value previously, as part of the error returned when trying to acquire the lock of a poisoned Mutex. I don't think clearing the flag could possibly cause a new problem that didn't exist before
21 March at 15:42 | Open on soc.punktrash.club
Corax

@Mara Awww, now I'm slightly disappointed it wasn't called cure_poison to stay in the metaphor ^^

21 March at 14:44 | Open on mastodon.social
Ray Gay :verified_bi:
Matthew Badger
kleines Filmröllchen

@Mara it's funny how they say "relatively minor release" and there's so much cool stuff in it regardless, especially the slicing and c string literals

21 March at 19:56 | Open on chaos.social
Go Up