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. If you find any errors in this week's issue, please submit a PR.

Updates from Rust Community

Newsletters

Project/Tooling Updates

Observations/Thoughts

Rust Walkthroughs

Crate of the Week

This week's crate is Qdrant, an open source production ready vector database/similarity search engine written in Rust. There are APIs available for Rust, Python, Javascript/Typescript and Go.

llogiq is overjoyed with his suggestion!

Please submit your suggestions and votes for next week!

Call for Participation

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.

Updates from the Rust Project

326 pull requests were merged in the last week

Rust Compiler Performance Triage

The last two weeks mostly have small changes across a number of benchmarks, no widespread large regressions or improvements.

Triage done by @simulacrum. Revision range: a368898d..3ea9ad532

6 Regressions, 3 Improvements, 4 Mixed; 2 of them in rollups 90 artifact comparisons made in total

Full report here

Approved RFCs

Changes to Rust follow the Rust RFC (request for comments) process. These are the RFCs that were approved for implementation this week:

New rustc and Cargo options to allow path sanitisation by default

Final Comment Period

Every week, the team announces the 'final comment period' for RFCs and key PRs which are reaching a decision. Express your opinions now.

RFCs

The #[diagnostic] attribute namespace

Tracking Issues & PRs

[disposition: merge] Allow limited access to OsStr bytes
[disposition: merge] Tracking Issue for #![feature(offset_of)]
[disposition: close] Tracking Issue for the x86 ud2 intrinsic
[disposition: merge] Document memory orderings of thread::{park, unpark}
[disposition: merge] Tracking Issue for BuildHasher::hash_one
[disposition: merge] Tracking Issue for #![feature(unix_chown)]

New and Updated RFCs

No New or Updated RFCs were created this week.

Call for Testing

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:

No RFCs issued a call for testing this week.

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.

Upcoming Events

Rusty Events between 2023-05-17 - 2023-06-14 🦀

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.

Jobs

Please see the latest Who's Hiring thread on r/rust

Quote of the Week

That's one of the great things about Rust: sometimes you can do something really dumb and get away with it.

– Rik Arends at RustNL

Thanks to Josh Triplett 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

Discuss on r/rust

Like what you see? Subscribe!