News for hackers. Stuff that matters.
Re:Rust 1.100.0 by Surac on Thursday November 12, 2026 @02:16PM (#50472661)
Still non ABI. Why is ist so hard? what is holding them back. Andy why does it need a unsave keyword? can't they marshal types like other languages?
Re:Rust 1.100.0 by adamch on Thursday November 12, 2026 @02:18PM (#50472696)
because they change the binary layout sometimes, and the benefits have not yet been judged to be worth freezing it.
Re:Rust 1.100.0 by vablings on Thursday November 12, 2026 @05:25PM (#50475233)
I mean they could also have a stable ABI for 2.0 and then and changes are breaking herein. Its kind of a choice problem
Re:Rust 1.100.0 by galangalalgol on Thursday November 12, 2026 @03:30PM (#50473765)
It is explained elsewhere, but a summary is that any language with generics is going to have any stable abi as a subset of the language. There is already a subset of the language that is a stable abi, it is the c abi. Expanding that subset has to be worth it in terms of what people actually want to export from a library. As I use generics fairly heavily I don't think I would use that expanded abi for anything.
Re:Rust 1.100.0 by kbolino on Thursday November 12, 2026 @04:02PM (#50474227)
You can marshal values, but you can't marshal lifetimes, ownership, (lack of) thread-safety, (lack of) side-effects, etc. The ABI carries far less information than the Rust compiler relies on. Thus, any FFI call is inherently unsafe. It takes you, the programmer, with knowledge the compiler doesn't have and the architecture doesn't provide, to determine whether the code as you use it actually is safe or not.