title = "New Year's Rust: A Call for Community Blogposts"

author = "The Rust Core Team"

'Tis the season for people and communities to reflect and set goals- and the Rust team is

title = "Help test Rust 2018"

author = "The Rust Core Team"

Back in July, we talked about ["Rust 2018"]. In short, we are launching a

layout = "post"

title = "The Governance WG is going public"

author = "The Rust Governance WG"

layout = "post"

title = "Laying the foundation for Rust's future"

author = "The Rust Core Team"

The Rust project was originally [conceived in 2010][2010] (depending on how you count, you might even say [2006][2006]!) as a [Mozilla Research] project, but the long term goal has always been to establish Rust as a self-sustaining project. In 2015, [with the launch of Rust 1.0][onepointoh], Rust established its project direction and governance independent of the Mozilla organization. Since then, Rust has been operating as an autonomous organization, with Mozilla being a prominent and consistent financial and legal sponsor.

layout = "post"

title = "Planning the 2021 Roadmap"

author = "The Rust Core Team"

The core team is beginning to think about the 2021 Roadmap, and we want to hear from the community. We’re going to be running two parallel efforts over the next several weeks: the 2020 Rust Survey, to be announced next week, and a call for blog posts.

layout = "post"

title = "Call for 2021 Roadmap Blogs Ending Soon"

author = "The Rust Core Team"

We will be closing the collection of blog posts on **October 5th**. As a reminder, we plan to close the [survey](https://blog.rust-lang.org/2020/09/10/survey-launch.html) on **September 24th**, later this week.

layout = "post"

title = "Marking issues as regressions"

author = "Camelid"

team = "the release team <https://www.rust-lang.org/governance/teams/operations#release>"

layout = "post"

title = "The Foundation Conversation"

author = "The Rust Core Team"

In August, we on the Core Team [announced our plans to create a Foundation](https://blog.rust-lang.org/2020/08/18/laying-the-foundation-for-rusts-future.html) by the end of the year. Since that time, we’ve been doing a lot of work but it has been difficult to share many details, and we know that a lot of you have questions.

layout = "post"

title = "Next steps for the Foundation Conversation"

author = "The Rust Core Team"

Last week we kicked off the [Foundation Conversation](https://blog.rust-lang.org/2020/12/07/the-foundation-conversation.html), a week-long period of Q&A forums and live broadcasts with the goal of explaining our vision for the Foundation and finding out what sorts of questions people had. We used those questions to help build a [draft Foundation FAQ](https://github.com/rust-lang/foundation-faq-2020/blob/main/FAQ.md), and if you’ve not seen it yet, you should definitely take a look -- it’s chock full of good information. Thanks to everyone for asking such great questions!

layout = "post"

title = "Rust Survey 2020 Results"

author = "The Rust Survey Team"

Greetings Rustaceans!

layout = "post"

title = "Crates.io Index Snapshot Branches Moving"

author = "The Crates.io Team"

Every so often, the [crates.io index](https://github.com/rust-lang/crates.io-index)'s Git history

title = "Non-lexical lifetimes (NLL) fully stable"

author = "Niko Matsakis"

team = "the NLL working group <https://www.rust-lang.org/governance/teams/compiler#Non-Lexical%20Lifetimes%20(NLL)%20working%20group>"

As of Rust 1.63 (releasing next week), the "non-lexical lifetimes" (NLL) work will be enabled by default. NLL is the second iteration of Rust's borrow checker. The [RFC] actually does quite a nice job of highlighting some of the motivating examples. "But," I hear you saying, "wasn't NLL included in [Rust 2018]?" And yes, yes it was! But at that time, NLL was only enabled for Rust 2018 code, while Rust 2015 code ran in "migration mode". When in "migration mode," the compiler would run both the old *and* the new borrow checker and compare the results. This way, we could give warnings for older code that should never have compiled in the first place; we could also limit the impact of any bugs in the new code. Over time, we have limited migration mode to be closer and closer to just running the new-style borrow checker: in the next release, that process completes, and all Rust code will be checked with NLL.

layout = "post"

title = "2022 Annual Rust Survey Results"

author = "The Rust Survey Working Group in partnership with the Rust Foundation"

Hello, Rustaceans!

layout = "post"

title = "A Call for Proposals for the Rust 2024 Edition"

author = "Ben Striegel on behalf of the Edition 2024 Project Group"

The year 2024 is soon to be upon us, and as long-time Rust aficionados know,

layout = "post"

author = "The Clippy Team"

layout = "post"

author = "David Wood"

description = "Highlighting a diagnostic improvement for async-await"

team = "the Async Foundations WG <https://rust-lang.github.io/compiler-team/working-groups/async-await/>"

layout = "post"

title = "Recent and future pattern matching improvements"

description = "Reviewing recent pattern matching improvements"

team = "the language team <https://www.rust-lang.org/governance/teams/lang>"

layout = "post"

title = "Keeping Rust projects secure with cargo-audit 0.18: performance, compatibility and security improvements"

description = "A look at the new features in cargo-audit 0.18 for ensuring dependencies are free of known vulnerabilities"

team = "the Secure Code WG <https://www.rust-lang.org/governance/wgs/wg-secure-code>"