Warning
This post was published 84 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 rustypaste, a minimal file upload/pastebin service.
Thanks to orhun 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.
ockam credential issue
command from Identity to IdentityIdentifier 2ockam project enroll
1ockam project ticket
should return a proper error message 1loopcrashbackoff
pods as possible targets 1If you are a Rust project owner and are looking for contributors, please submit tasks here.
410 pull requests were merged in the last week
fix(resolve)
: skip assertion judgment when NonModule is dummythir
: Add Become
expression kind-Zremark-dir
unstable flag to write LLVM optimization remarks to YAMLConstKind::Value(_)
to in_operand()
move
for borrows that aren't closuresDefKind::ImplTraitPlaceholder
rustc_mir_dataflow
dropping_copy_types
lint from linting in match-arm with side-effectse_flags
in ELF files generated for AVR targetsproc_macro_span
Elaboratable
trait take clausesvariances_of
for RPITIT GATslice::swap
for mem::swap(&mut x[0], &mut x[1])
borrowck errorfor<'a>
inline(always)
simd_shuffle_indices
use valtreesUnwindAction::Continue
explicit in MIR dump--quiet
actually do somethingUnique
fn_abi
#[cold]
attributeBox
es with different allocatorsrustc_on_unimplemented
std-agnosticconst_cstr_methods
single_line_let_else_max_width
manual_try_fold
,
needless_raw_string_hashes
,
redundant_at_rest_pattern
,
tuple_array_conversions
,
manual_range_patterns
,
type_id_on_box
,
needless_pub_self
, pub_with_shorthand
and pub_without_shorthand
significant_drop_tightening
: fix incorrect suggestionarc_with_non_send_sync
: don't lint if type has nested type parameterslet_and_return
: lint 'static
lifetimes, don't lint borrows in closuresmissing_fields_in_debug
: make sure self type is an adtneedless_raw_string_hashes
: only reset hashes needed if not following quoteoption_if_let_else
: suggest .as_ref()
if scrutinee is of type &Option<_>
question_mark
: don't lint inside of try
blockunused_async
: don't lint if function is part of a traituseless_vec
: add more tests and don't lint inside of macrosuseless_vec
: use the source span for initializermanual_let_else
in cases where ?
would workeq_op
suggest .is_nan()
is_some_and
over map().unwrap
noImplicitOverride
ts option@tsconfig/strictest
to define type checking rulesself
and super
path resolution in block moduleshandle_code_action
#[tokio::test]
#[derive_const(Trait)]
A quiet week, with a mixed set of improvements and regressions. Overall slightly more improvements than regressions.
Triage done by @simulacrum. Revision range: b5e51db16..52d8c490
4 Regressions, 4 Improvements, 2 Mixed; 0 of them in rollups
51 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.
unsafe_code
lint into lint groupf16
and f128
float typesAn 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-07-05 - 2023-08-02 🦀
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
I'm not here to tell you that Rust is the best language....... you should have figured that out by now.
Thanks to newpavlov 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