Publish project-goals.md

content/posts/performance3-yellow-submarine.md

@@ -1,5 +1,5 @@
 ---
-title: 'Performance3 Yellow Submarine'
+title: 'Performance3 '
 date: 2024-05-02T22:38:17+02:00
 draft: true
 ---
@@ -12,6 +12,4 @@ NOTE: As a Clippy team member, the part of the compiler that I'm most familiar w
 
 > We have about 800 lints, and each one of those have to be processed on every run... What if instead of having to do all that effort, we just filtered lints that won't emit a warning beforehand? :thinking:
 
-That's what I thought ~8 months ago. And after 4 feature branches, about 30 commits, **a whole lot** of testing and debugging, and running the same benchmarking commands about a trillion times, we have... [An almost finished feature branch](https://github.com/blyxyas/rust/tree/ignore-allowed-lints-final). It's not much, but it's honest work :sweat_smile:
-
-Due to how to compiler is built, this kind of change is difficult. Mastering things like [queries](https://github.com/rust-lang/rust/blob/master/compiler/rustc_middle/src/query/mod.rs), seeing where things are run, trying to generate useful [`flamegraph`](https://crates.io/crates/flamegraph)s (which is pretty difficult for a compiler).
+That's what I thought ~8 months ago. And after 4 feature branches, about 40 temporary commits, **a whole lot** of testing and debugging, and running the same benchmarking commands about a trillion times, we have... [An almost finished feature branch](https://github.com/blyxyas/rust/tree/ignore-allowed-lints-final). It's not much, but it's honest work :sweat_smile:

content/posts/project-goals.md

@@ -0,0 +1,17 @@
+---
+title: "Rust project goals & what's coming"
+date: 2024-07-15T19:33:37+02:00
+draft: false
+---
+
+The Rust organization is starting an initiative for "project goals", in which every team submits a list of goals that they'd like to achieve in the coming months. I talked with my team on Zulip and got our hands dirty drafting a list of goals for 2024's second half. You can read the final document [here](https://rust-lang.github.io/rust-project-goals/2024h2/optimize-clippy.html).
+
+After receiving feedback and merging a few PRs to the project goals repo, and receiving a general ":+1:" from the team, we're adding "Optimizing Clippy & linting" to Rust's RFC for project goals 2024H2.
+
+**This is great news!** Now the Clippy Performance Project that I talked about in other blog posts is finally formalized and held to a standard (+ anyone that wants to help, is greatly welcomed!).
+
+You can read the other project goals on the [RFC PR](https://github.com/rust-lang/rfcs/pull/3672), that will eventually get merged as RFC #3672
+
+So yeah, if you want to read more about the "Optimizing Clippy & Linting" project goal, check out [the book](https://rust-lang.github.io/rust-project-goals/2024h2/optimize-clippy.html).
+
+Peace! ✌️ :heart: