Info
This post is auto-generated from RSS feed This Week in Rust. Source: This Week in Rust 573
Hello and welcome to another issue of This Week in Rust! Rust is a programming language empowering everyone to build reliable and efficient software. This is a weekly summary of its progress and community. Want something mentioned? Tag us at @ThisWeekInRust on X (formerly Twitter) or @ThisWeekinRust on mastodon.social, or send us a pull request. Want to get involved? We love contributions.
This Week in Rust is openly developed on GitHub and archives can be viewed at this-week-in-rust.org. If you find any errors in this week's issue, please submit a PR.
Want TWIR in your inbox? Subscribe here.
This week's crate is struct-split, a proc macro to implement partial borrows.
Thanks to Felix for the suggestion!
Please submit your suggestions and votes for next week!
An important step for RFC implementation is for people to experiment with the implementation and give feedback, especially before stabilization. The following RFCs would benefit from user testing before moving forward:
If you are a feature implementer and would like your RFC to appear on the above list, add the new call-for-testing
label to your RFC along with a comment providing testing instructions and/or guidance on which aspect(s) of the feature
need testing.
Always wanted to contribute to open-source projects but did not know where to start? Every week we highlight some tasks from the Rust community for you to pick and get started!
Some of these tasks may also have mentors available, visit the task page for more information.
take
and replace
for Context and Extensions](https://github.com/plabayo/rama/issues/353If you are a Rust project owner and are looking for contributors, please submit tasks here or through a PR to TWiR or by reaching out on X (formerly Twitter) or Mastodon!
Are you a new or experienced speaker looking for a place to share something cool? This section highlights events that are being planned and are accepting submissions to join their event as a speaker.
If you are an event organizer hoping to expand the reach of your event, please submit a link to the website through a PR to TWiR or by reaching out on X (formerly Twitter) or Mastodon!
403 pull requests were merged in the last week
wasm32-wasi
target from rustcwide-arithmetic
feature for WebAssembly{ignore,needs}-{rustc,std}-debug-assertions
directive supportCodegenBackend::link
create_object_file
llvm_cov
{
and }
.into_iter()
on iteratorsmaybe_unwrap_block
when checking for macro calls in a block expruse<impl Trait>
when we have an edition-2024-related borrowck issuecheck_opaque_type_well_formed
RustString
an extern type to avoid improper_ctypes
warningsTy::primitive_symbol
recognize str
fn_abi_sanity_check
a bit stricterpub(super)
in unreachable_pub
lint suggestionE::assoc
when we encounter E::Variant::assoc
'
, like regular lifetimes dorustc_session::config::rustc_short_optgroups
rustc_safe_intrinsic
attribute; use rustc_intrinsic
functions insteadenum
glob-imports from rustc_middle::ty
const_impl_trait
gate for all conditional and trait const callsHEAP
static in Windows alloc-Ztime-llvm-passes
and -Zprint-codegen-stats
PartialEq<lhs_ty>
download-rustc="if-unchanged"
as a global defaultpointee_info_at
: fix logic for recursing into enumsrustc_codegen_llvm
: Add a new 'pc' option to branch-protectionrustc_target
: more target string fixes for LLVM 20get_alloc_info
: also return mutabilityconst_char_encode_utf16
multivalue
, reference-types, and tail-call
target featuresUnsafeCell::from_mut
const_eq_ignore_ascii_case
char::is_whitespace
unstably conststr::repeat
div_ceil
for NonZero<unsigned>
file_lock
featureBlock
s directly on the heapf16
on platforms that have recursion problemstarget
pathsfield_visibility
not called for new-type aliasesunsafe_op_in_unsafe_fn
when using dynamic librarys and wrap_unsafe_ops
no_mangle_with_rust_abi
: properly position the suggested ABIclippy::question_mark
large_include_file
lint being triggered all the time by doc commentsidentity_op
suggestions use correct parenthesisRegressions primarily in doc builds. No significant changes in cycle or max-rss counts.
Triage done by @simulacrum. Revision range: 27e38f8f..d4822c2d
1 Regressions, 1 Improvements, 4 Mixed; 1 of them in rollups 47 artifact comparisons made in total
Changes to Rust follow the Rust RFC (request for comments) process. These are the RFCs that were approved for implementation this week:
Every week, the team announces the 'final comment period' for RFCs and key PRs which are reaching a decision. Express your opinions now.
const_size_of_val
and const_align_of_val
const <*const T>::is_null
Pin
methodsconst_atomic_from_ptr
Rusty Events between 2024-11-13 - 2024-12-11 🦀
If you are running a Rust event please add it to the calendar to get it mentioned here. Please remember to add a link to the event too. Email the Rust Community Team for access.
Please see the latest Who's Hiring thread on r/rust
Netstack3 encompasses 63 crates and 60 developer-years of code. It contains more code than the top ten crates on crates.io combined. ... For the past eleven months, they have been running the new networking stack on 60 devices, full time. In that time, Liebow-Feeser said, most code would have been expected to show "mountains of bugs". Netstack3 had only three; he attributed that low number to the team's approach of encoding as many important invariants in the type system as possible.
– Joshua Liebow-Feeser at RustConf, as reported by Daroc Alden on Linux Weekly News
Thanks to Anton Fetisov for the suggestion!
Please submit quotes and vote for next week!
This Week in Rust is edited by: nellshamrell, llogiq, cdmistman, ericseppanen, extrawurst, andrewpollack, U007D, kolharsam, joelmarcey, mariannegoldin, bennyvasquez.
Email list hosting is sponsored by The Rust Foundation
🏷️ Rust_feed