Series: The Rust Annals
Vol. I Issue 78 nlopes.dev
Announcing Rust 1.77.0
C-string literals and async recursion removal significantly improve FFI safety and concurrency patterns, backed by the stabilization of offset_of! and other ergonomic APIs.
C-string literals
Rust now supports C-string literals (c"abc") which expand to a nul-byte
terminated string in memory of type &'static CStr. This makes it easier to write code
interoperating with foreign language interfaces which require nul-terminated
strings, with all of the relevant error checking (e.g., lack of interior nul
byte) performed at compile time.
Support for recursion in async fn
Async functions previously could not call themselves due to a compiler limitation. In 1.77, that limitation has been lifted, so recursive calls are permitted so long as they use some form of indirection to avoid an infinite size for the state of the function.
This means that code like this now works:
async fn fib(n: u32) -> u32 {
match n {
0 | 1 => 1,
_ => Box::pin(fib(n-1)).await + Box::pin(fib(n-2)).await
}
}
offset_of!
1.77.0 stabilizes offset_of! for struct fields, which provides access to the
byte offset of the relevant public field of a struct. This macro is most useful
when the offset of a field is required without an existing instance of a type.
Implementing such a macro is already possible on stable, but without an
instance of the type the implementation would require tricky unsafe code which
makes it easy to accidentally introduce undefined behavior.
Users can now access the offset of a public field with offset_of!(StructName, field). This expands to a usize expression with the offset in bytes from the
start of the struct.
Enable strip in release profiles by default
Cargo profiles
which do not enable debuginfo in
outputs (e.g., debug = 0) will enable strip = "debuginfo" by default.
This is primarily needed because the (precompiled) standard library ships with debuginfo, which means that statically linked results would include the debuginfo from the standard library even if the local compilations didn’t explicitly request debuginfo.
Users which do want debuginfo can explicitly enable it with the debug flag in the relevant Cargo profile.