Added links from each section back to its description in the February post, in order to supply people with context to understand each item.

Author: pnkfelix

posts/inside-rust/2022-08-08-compiler-team-2022-midyear-report.md

@@ -188,6 +188,8 @@ presentation here.
 
 ### I-unsound issues (🦀)
 
+[Description from February](https://blog.rust-lang.org/inside-rust/2022/02/22/compiler-team-ambitions-2022.html#i-unsound-issues-)
+
 <!-- https://hackmd.io/@rust-compiler-team/r1Abdj7uq -->
 
 **Progress:** The Rust project has made progress on this ambition since the start of the year.
@@ -216,6 +218,8 @@ It is not effective to fix bugs that users will never encounter in practice when
 
 ### async traits
 
+[Description from Feburary](https://blog.rust-lang.org/inside-rust/2022/02/22/compiler-team-ambitions-2022.html#async-traits)
+
 <!-- https://hackmd.io/@rust-compiler-team/H1eW9oXdc -->
 
 **Progress:** The Rust project has made progress on this ambition since the start of the year.
@@ -247,6 +251,8 @@ We have an async stakeholders group that we use for this kind of input, but have
 
 ### async crashdump dissection
 
+[Description from Feburary](https://blog.rust-lang.org/inside-rust/2022/02/22/compiler-team-ambitions-2022.html#async-crashdump-dissection)
+
 <!-- https://hackmd.io/@rust-compiler-team/SJYL9iQ_9 -->
 
 **Progress:** The Rust project has made progress on this ambition since the start of the year, but we do not think this year’s planned goals for this ambition will be achieved in the next six months. We think a solution will be available in the next two years, but not sooner than six months.
@@ -268,6 +274,8 @@ The two main obstacles are:
 
 ### wg-debugging
 
+[Description from Feburary](https://blog.rust-lang.org/inside-rust/2022/02/22/compiler-team-ambitions-2022.html#debugging-initiatives-)
+
 <!-- https://hackmd.io/@rust-compiler-team/HJOtiiQOq -->
 
 **Progress:** The Rust project has made progress on this ambition since the start of the year
@@ -285,6 +293,8 @@ and we have completed some of our milestones. Furthermore, (some of) our work ha
 
 ### improving debuginfo quality
 
+[Description from Feburary](https://blog.rust-lang.org/inside-rust/2022/02/22/compiler-team-ambitions-2022.html#debugging-initiatives-)
+
 <!-- https://hackmd.io/@rust-compiler-team/HJQ25sXOq -->
 
 **Progress:** The Rust project has made progress on this ambition since the start of the year
@@ -319,6 +329,8 @@ team.
 
 ### supporting split debuginfo
 
+[Description from Feburary](https://blog.rust-lang.org/inside-rust/2022/02/22/compiler-team-ambitions-2022.html#debugging-initiatives-)
+
 <!-- https://hackmd.io/@rust-compiler-team/ByXfjiXu5 -->
 
 **Progress:** The Rust project has not made any progress on this ambition since the start of the year (@pnkfelix: but the free form answer somewhat contradicts this)
@@ -339,6 +351,8 @@ The owner of this work, @davidtwco, intends to stick with the theme of debugging
 
 ### better integration with trace-based debuggers
 
+[Description from Feburary](https://blog.rust-lang.org/inside-rust/2022/02/22/compiler-team-ambitions-2022.html#debugging-initiatives-)
+
 <!-- https://hackmd.io/@rust-compiler-team/BkJSsi7d5 -->
 
 **Progress:** The Rust project has not made any progress on this ambition since the start of the year.
@@ -361,6 +375,8 @@ control flow where that specific character was emitted to stdout/stderr.
 
 ### Faster Builds Initiatives (👩‍💻, 🛠️)
 
+[Description from Feburary](https://blog.rust-lang.org/inside-rust/2022/02/22/compiler-team-ambitions-2022.html#faster-builds-initiatives--%EF%B8%8F)
+
 <!-- https://hackmd.io/@rust-compiler-team/B1O2siXd9 -->
 
 **Progress:** The Rust project has made progress on this ambition since the start of the year, and we think this year’s planned goals for this ambition will be achieved in the next six months. (Note that also we think our chosen problem is never-ending and will never be “resolved”.)
@@ -386,6 +402,8 @@ control flow where that specific character was emitted to stdout/stderr.
 
 ### Generic Associated Types
 
+[Description from Feburary](https://blog.rust-lang.org/inside-rust/2022/02/22/compiler-team-ambitions-2022.html#expressiveness-initiatives--)
+
 <!-- https://hackmd.io/@rust-compiler-team/BkM83iX_9 -->
 
 **Progress:** The Rust project has made progress on this ambition since the start of the year
@@ -409,6 +427,8 @@ If @jackh726 hadn’t been working on GATs for the past year or so, they would h
 
 ### safe transmute
 
+[Description from Feburary](https://blog.rust-lang.org/inside-rust/2022/02/22/compiler-team-ambitions-2022.html#expressiveness-initiatives--)
+
 <!-- https://hackmd.io/@rust-compiler-team/HJ7Y3s7uq -->
 
 **Progress:** The Rust project has made progress on this ambition since the start of the year
@@ -443,6 +463,8 @@ With the mentoring provided by @oli-obk and an influx of interest and help from
 
 ### Chalk
 
+[Description from Feburary](https://blog.rust-lang.org/inside-rust/2022/02/22/compiler-team-ambitions-2022.html#chalk)
+
 <!-- https://hackmd.io/@rust-compiler-team/HyVh2sQdq -->
 
 **Progress:** The Rust project has made progress on this ambition since the start of the year
@@ -467,6 +489,8 @@ We have completed some of our milestones.
 
 ### P-high Backlog Processing Aspirations (🦀)
 
+[Description from Feburary](https://blog.rust-lang.org/inside-rust/2022/02/22/compiler-team-ambitions-2022.html#p-high-aspirations-)
+
 <!-- https://hackmd.io/@rust-compiler-team/SkS1psm_c -->
 
 **Progress:** The Rust project has made progress on this ambition since the start of the year
@@ -490,6 +514,8 @@ We think a solution will be available in the next two years, but not sooner than
 
 ### Debugging Aspirations (👩‍💻)
 
+[Description from Feburary](https://blog.rust-lang.org/inside-rust/2022/02/22/compiler-team-ambitions-2022.html#debugging-aspirations-)
+
 <!-- https://hackmd.io/@rust-compiler-team/SyM2poXu9 -->
 
 **Progress:** The Rust project has made progress on this ambition since the start of the year
@@ -522,6 +548,8 @@ There isn't much focus happening here currently.
 
 ### Incremental Compilation Aspirations
 
+[Description from Feburary](https://blog.rust-lang.org/inside-rust/2022/02/22/compiler-team-ambitions-2022.html#incremental-compilation-aspirations)
+
 <!-- https://hackmd.io/@rust-compiler-team/B1D7CiX_c -->
 
 **Progress:**
@@ -563,6 +591,8 @@ This refactor allowed for faster progress in fixing a few old bugs.
 
 ### Inter-crate Sharing Aspirations
 
+[Description from Feburary](https://blog.rust-lang.org/inside-rust/2022/02/22/compiler-team-ambitions-2022.html#inter-crate-sharing-aspirations)
+
 <!-- https://hackmd.io/zad1BjIoR8S4IfE49z-xYg -->
 <!-- (no survey response as of 2022-07-19) -->
 
@@ -575,6 +605,8 @@ are hard to push forward right now due to lack of reviewing capacity.
 
 ### const generics and const eval
 
+[Description from Feburary](https://blog.rust-lang.org/inside-rust/2022/02/22/compiler-team-ambitions-2022.html#expressiveness-aspirations--)
+
 <!-- https://hackmd.io/@rust-compiler-team/HktiComdq -->
 
 **Progress:** The Rust project has made progress on this ambition since the start of the year.
@@ -595,6 +627,8 @@ are hard to push forward right now due to lack of reviewing capacity.
 
 ### MIR tooling (stable-mir and ghost-code)
 
+[Description from Feburary](https://blog.rust-lang.org/inside-rust/2022/02/22/compiler-team-ambitions-2022.html#mir-tooling)
+
 <!-- https://hackmd.io/CWcHnbOWReSUyPv0ZDdWaw -->
 
 **Progress:** The Rust project has made progress on this ambition since the start of the year, but we do not think this year’s planned goals for this ambition will be achieved in the next six months.
@@ -617,6 +651,8 @@ Work has not yet started but the we believe that we have a solution.
 
 #### MCVE reduction tooling
 
+[Description from Feburary](https://blog.rust-lang.org/inside-rust/2022/02/22/compiler-team-ambitions-2022.html#mcve-reduction-tooling)
+
 <!-- https://hackmd.io/@rust-compiler-team/r19rJhmu5 -->
 
 **Progress:** The Rust project has not made any progress on this ambition since the start of the year
@@ -633,6 +669,8 @@ However, they have not dedicated any time to solving the problem.
 
 #### Performance Dashboard
 
+[Description from Feburary](https://blog.rust-lang.org/inside-rust/2022/02/22/compiler-team-ambitions-2022.html#performance-dashboard)
+
 <!-- https://hackmd.io/@rust-compiler-team/SyaDJ2X_5 -->
 
 **Progress:** The Rust project has made progress on this ambition since the start of the year
@@ -664,6 +702,8 @@ We had long-standing debt on Crater and triagebot that needed to be addressed, a
 
 #### Ease writing new backends via intrinsic MIR fallbacks
 
+[Description from Feburary](https://blog.rust-lang.org/inside-rust/2022/02/22/compiler-team-ambitions-2022.html#ease-writing-new-backends)
+
 <!-- https://hackmd.io/@rust-compiler-team/HylMg2m_9 -->
 
 **Progress:** The Rust project has made progress on this ambition since the start of the year
@@ -686,6 +726,8 @@ Mentoring instructions, or even steps with minimal details, might help non-exper
 
 #### Cranelift
 
+[Description from Feburary](https://blog.rust-lang.org/inside-rust/2022/02/22/compiler-team-ambitions-2022.html#cranelift)
+
 <!-- https://hackmd.io/@rust-compiler-team/BJLre2Xu9 -->
 
 **Progress:** The Rust project has made progress on this ambition since the start of the year.
@@ -707,6 +749,8 @@ With the codegen phase of debug mode builds getting faster with cg_clif in most
 
 #### GCC backend
 
+[Description from Feburary](https://blog.rust-lang.org/inside-rust/2022/02/22/compiler-team-ambitions-2022.html#gcc-backend)
+
 <!-- https://hackmd.io/T03Nu92NSLeyyYnnW3XFyg -->
 
 **Progress:** The Rust project has made progress on this ambition since the start of the year
@@ -739,6 +783,8 @@ When the GCC backend is good enough and when the Rust for Linux project is ready
 
 ### Diagnostics Aspirations (👩‍💻)
 
+[Description from Feburary](https://blog.rust-lang.org/inside-rust/2022/02/22/compiler-team-ambitions-2022.html#diagnostics-aspirations-)
+
 <!-- https://hackmd.io/@rust-compiler-team/HJ_cgnXd5 -->
 
 **Progress:** The Rust project has made progress on this ambition since the start of the year