Info
This post is auto-generated from RSS feed This Week in Rust. Source: This Week in Rust 510
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 dprint, a fast code formatter that formats Markdown, TypeScript, JavaScript, JSON, TOML and many other types natively via Wasm plugins.
Thanks to Martin Geisler 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.
cssparser
& selectors
class
attributesIf you are a Rust project owner and are looking for contributors, please submit tasks here.
366 pull requests were merged in the last week
aligned_alloc
MaybeUninit
in input and output of inline assembly#[repr(Rust)]
suggestion
for some #[deprecated]
itemspush_trailing
functionptr::write
s for the invalid_reference_casting
lintExpnId
for concurrent decodinglarge_assignments
lintsSyntaxContext
decodinginvalid_reference_casting
lintbreak rust;
include_bytes!
directly into an LrcSharded
an enum
and specialize it for the single thread caserustc_on_unimplemented
std-agnostic for alloc::rc
type_of
on opaqueforce_allocation
to_pretty_impl_header
involving only anon lifetimespoint_at_path_if_possible
ELIDED_LIFETIMES_IN_ASSOCIATED_CONSTANT
)generics_of
to smirpredicates_of
StatementKind::Coverage
as completely opaque for SMIR purposesNameBinding
s on every use, create them once per definition insteadpthread_t
handle leakDuration::checked_div
HashMap
s that use a custom allocator&
to &mut
where applicableClone
by removing redundant guardstarget.'cfg(..)'.linker
--keep-going
--no-html-source
flagimplied_bounds_in_impls
reserve_after_initialization
arithmetic_side_effects
: detect division by zero for Wrapping
and Saturating
if_then_some_else_none
: look into local initializers for early returnsiter_overeager_cloned
: detect .cloned().all()
and .cloned().any()
unnecessary_unwrap
: lint on .as_ref().unwrap()
implements_trait_with_env_from_iter
"derivable_impls
: attributes are ignored"tuple_array_conversions
lint on nightlyfloat_cmp
check if lhs is a custom type#[allow(unused_braces)]
A fairly quiet week, with improvements exceeding a small scattering of regressions. Memory usage and artifact size held fairly steady across the week, with no regressions or improvements.
Triage done by @simulacrum. Revision range: d4a881e..cedbe5c
2 Regressions, 3 Improvements, 2 Mixed; 0 of them in rollups 108 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.
PATH
option for --print KIND=PATH
Iterator::sum
on Range<u*>
and RangeInclusive<u*>
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-30 - 2023-09-27 ๐ฆ
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
In [other languages], I could end up chasing silly bugs and waste time debugging and tracing to find that I made a typo or ran into a language quirk that gave me an unexpected nil pointer. That situation is almost non-existent in Rust, it's just me and the problem. Rust is honest and upfront about its quirks and will yell at you about it before you have a hard to find bug in production.
Thanks to Kyle Strand 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