Warning
This post was published 56 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 allocator-api2, a forward-compatibility shim to use the nightly allocator API on stable Rust.
Thanks to Zicklag for the 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.
upsert
endpoint to cards_info
tableIf you are a Rust project owner and are looking for contributors, please submit tasks here.
404 pull requests were merged in the last week
x86_64-unikraft-linux-musl
targetencode_const
: unexpected type usizebinary_search_slice
builtin_macros
: expect raw strings toocodegen_ssa
cleanupsdesugar_doc_comments
cleanupssimd_bswap, simd_bitreverse, simd_ctlz,
and simd_cttz
intrinsics<&NotClone as Clone>::clone()
calls and suggest to add Clone trait appropriatelyCMAKE_SYSTEM_NAME
on a cross build targeting DragonFlyimpl Trait
in trait methods with no body-Zwrite-long-types-to-disk=no
for ui-fulldeps --stage=1
host
param in diagnosticssimd_bswap
for i8/u8use
and extern crate
itemsToString
implementations that specialize the default oneremove_matches
TokenTree
cloning()
return type checksassumed_wf_types
of their parent method--error-format human-annotate-rs
handle multiple files--print
with path unstablenoop_method_call
warn by defaultlazy_type_alias
as incompleteUnsize
goal in the new solverTokenKind::clone
constness
from ParamEnv
Option
,Result
}::as_ref()
instead of cloned()
in some casesunnameable_types
lintconst-weak-new
NonNull::as_ref
AtomicBool
for target that don't support byte-sized atomicsmap_or
as #[must_use]
io::Sink
into io::Empty
len
method for UnboundedSender
ssh://
impl Sized
& impl ?Sized
clone()
calls for derive_id
dyn*
syntax when rewriting ast::TyKind::TraitObject
arc_with_non_send_sync
: no longer lints macro-generated codearithmetic_side_effects
: ignore paths referring to literalsneedless_pass_by_ref_mut
: do not lint if passed as a fn-like argumentredundant_closure
fixesslow_vector_initialization
: catch Vec::new()
followed by .resize(len, 0)
unnecessary_find_map
: look for then_some
needless_pass_by_ref_mut
: emit note if function is behind a #[cfg]
filter_map_bool_then
readonly_write_lock
option_env_unwrap
warns even if a variable isn't set at compiletimeeager_macro_recur
Self
without field in mir loweringChanges 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.
unconditional_recursion
warning detect recursive dropsint_roundings
ManuallyDrop
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.
Rusty Events between 2023-08-02 - 2023-08-30 ๐ฆ
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
Writing return \<something>; at the end of a function in Rust is a bit like answering the question "Do you like potatoes?" with "Yes, I like potatoes" instead of simple "Yes".
โ Artem Borisovskiy on rust-users
Thanks to Todd Fleming 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