Warning
This post was published 42 days ago. The infomation described in this article may have changed.
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 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.
This week's crate is agree, a command-line tool implementing Shamir's Secret Sharing.
Thanks to Alexander Weber for the self-suggestion!
Please submit your suggestions and votes for next week!
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.
If you are a Rust project owner and are looking for contributors, please submit tasks here.
344 pull requests were merged in the last week
riscv-interrupt-{m,s}
calling conventionsmax_atomic_width
for AVR to 16max_atomic_width
for sparc-unknown-linux-gnu to 32cvar.wait_while
Expr::can_have_side_effects()
is incorrect for struct/enum/array/tuple literalsrustc_data_structures
: base_n
perf: remove unnecessary utf8 checkoffset_of
: guard against invalid use (with unsized fields)mir_drops_elaborated
querymem::transmute
with the invalid_reference_casting
lint__rust_alloc_error_handler_should_panic
more than oncerust.codegen-backends
on deserializationpredicates_for_object_candidate
impl const
to bind to host effect paramCString
for FFI;
that parses as function calltype_of
to determine if item has intrinsic shiminternal_features
to warn*const [type error] does not implement the Copy trait
global_allocator
expansionunconditional_recursion
warning detect recursive dropstrait_ref_is_knowable
in new solvertry_coerce
in new solverSOCK_SEQPACKET+CMSG
ImplSource::Param
resolve_vars_with_obligations
opt-dist
#[expect]
the same way #[allow]
is with the dead_code
lintcompare_method_predicate_entailment
DefKind
Arc
on !Send
/!Sync
typesllvm-profdata
binary in opt-dist
#[macro_export]
is applied on decl macrosabi_thiscall
<*const T>::sub
cannot overflowOption::take_if
ptr::Unique
in LinkedList
codeascii::Char
methods from as_
to to_
Debug
for Vars
and VarsOs
int_roundings
Iterator::map_windows
compare_bytes
intrinsic instead of calling memcmp
directlyf32
and f64
--help
easier to browseTargetInfo
--nocapture
flag if cargo test
process is terminated via a signalgeneric-simd
featuremacro_rules!
definitions--file-lines
helpiter_overeager_cloned
: detect .cloned().filter()
and .cloned().find()
filter_map_bool_then
: Don't ICE on late bound regionsmanual_retain
: add lint case for binary_heap
redundant_guards
: don't lint on float literalsredundant_locals
: fix FPs on mutated shadows(dead_code, unused_imports,
...)only_types
config filtering out traits from world symbols#[cfg]
s on generic parametersconvert_named_struct_to_tuple_struct
A light week. Main thing to report is we got some improvements from telling LLVM
that the negation in <*const T>::sub
cannot overflow.
Triage done by @pnkfelix. Revision range: 443c3161..e8459109
0 Regressions, 1 Improvements, 4 Mixed; 1 of them in rollups 49 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.
#[repr(Rust)]
Or
pattern without allocating placescheduled_removal
Parameter for deprecated
AttributeAn 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.
Rusty Events between 2023-08-16 - 2023-09-13 🦀
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
It has been
0
days since someone tried and failed to use unsafe to circumvent the lifetime system.
Thanks to mdHMUpeyf8yluPfXI 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