Skip to content

Commit fc6b535

Browse files
nikomatsakisnikomatsakis
committed
link tracking issues
1 parent 0aa7eec commit fc6b535

26 files changed

+201
-151
lines changed

‎src/2024h2/ATPIT.md‎

Lines changed: 7 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -1,10 +1,12 @@
11
# Associated type position impl trait
22

3-
| Metadata | |
4-
| -------- | --------------- |
5-
| Owner(s) | @oli-obk |
6-
| Teams | [types], [lang] |
7-
| Status | Accepted |
3+
| Metadata | |
4+
| --- | --- |
5+
| Owner(s) | @oli-obk |
6+
| Teams | [types], [lang] |
7+
| Status | Accepted |
8+
| Tracking issue | [rust-lang/rust-project-goals#103] |
9+
810

911
## Summary
1012

‎src/2024h2/Patterns-of-empty-types.md‎

Lines changed: 8 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -1,10 +1,12 @@
11
# Patterns of empty types
22

3-
| Metadata | |
4-
| -------- | ---------- |
5-
| Owner(s) | @Nadrieril |
6-
| Teams | [lang] |
7-
| Status | Accepted |
3+
| Metadata | |
4+
| --- | --- |
5+
| Owner(s) | @Nadrieril |
6+
| Teams | [lang] |
7+
| Status | Accepted |
8+
| Tracking issue | [rust-lang/rust-project-goals#115] |
9+
810

911
## Summary
1012

@@ -109,4 +111,4 @@ Note:
109111

110112
[`exhaustive_patterns`]: https://github.com/rust-lang/rust/issues/51085
111113
[`min_exhaustive_patterns`]: https://github.com/rust-lang/rust/issues/119612
112-
[`never_patterns`]: https://github.com/rust-lang/rust/issues/118155
114+
[`never_patterns`]: https://github.com/rust-lang/rust/issues/118155

‎src/2024h2/Polonius.md‎

Lines changed: 7 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -1,10 +1,12 @@
11
# Scalable Polonius support on nightly
22

3-
| Metadata | |
4-
| -------- | -------- |
5-
| Owner(s) | @lqd |
6-
| Teams | [types] |
7-
| Status | Accepted |
3+
| Metadata | |
4+
| --- | --- |
5+
| Owner(s) | @lqd |
6+
| Teams | [types] |
7+
| Status | Accepted |
8+
| Tracking issue | [rust-lang/rust-project-goals#118] |
9+
810

911
## Summary
1012

‎src/2024h2/Project-goal-slate.md‎

Lines changed: 8 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -1,10 +1,12 @@
11
# Assemble project goal slate
22

3-
| Metadata | |
4-
| -------- | -------------------- |
5-
| Owner(s) | @nikomatsakis |
6-
| Teams | [leadership-council] |
7-
| Status | Accepted |
3+
| Metadata | |
4+
| --- | --- |
5+
| Owner(s) | @nikomatsakis |
6+
| Teams | [leadership-council] |
7+
| Status | Accepted |
8+
| Tracking issue | [rust-lang/rust-project-goals#102] |
9+
810

911
*Extracted from [RFC 3614](https://github.com/rust-lang/rfcs/blob/master/text/3614-project-goals.md)*
1012

@@ -178,4 +180,4 @@ Simply put, no. The owner will review the goals and ensure a quality slate, but
178180

179181
### Why the six months horizon?
180182

181-
Per the previous points, it is helpful to have a "season" for goals, but having e.g. an annual process prevents us from reacting to new ideas in a nimble fashion. At the same time, doing quarterly planning, as some companies do, is quite regular overhead. Six months seemed like a nice compromise, and it leaves room for a hefty discussion period of about 2 months, which sems like a good fit for an open-source project.
183+
Per the previous points, it is helpful to have a "season" for goals, but having e.g. an annual process prevents us from reacting to new ideas in a nimble fashion. At the same time, doing quarterly planning, as some companies do, is quite regular overhead. Six months seemed like a nice compromise, and it leaves room for a hefty discussion period of about 2 months, which sems like a good fit for an open-source project.

‎src/2024h2/Rust-2024-Edition.md‎

Lines changed: 7 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -1,10 +1,12 @@
11
# Rust 2024 Edition
22

3-
| Metadata | |
4-
| -------- | --------------- |
5-
| Owner(s) | @traviscross |
6-
| Teams | [lang], [types] |
7-
| Status | Flagship |
3+
| Metadata | |
4+
| --- | --- |
5+
| Owner(s) | @traviscross |
6+
| Teams | [lang], [types] |
7+
| Status | Flagship |
8+
| Tracking issue | [rust-lang/rust-project-goals#117] |
9+
810

911
## Summary
1012

‎src/2024h2/Rust-for-SciComp.md‎

Lines changed: 8 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -1,10 +1,12 @@
11
# Expose experimental LLVM features for automatic differentiation and GPU offloading
22

3-
| Metadata | |
4-
| -------- | ------------------ |
5-
| Owner(s) | @ZuseZ4 |
6-
| Teams | [lang], [compiler] |
7-
| Status | Accepted |
3+
| Metadata | |
4+
| --- | --- |
5+
| Owner(s) | @ZuseZ4 |
6+
| Teams | [lang], [compiler] |
7+
| Status | Accepted |
8+
| Tracking issue | [rust-lang/rust-project-goals#109] |
9+
810

911
## Summary
1012

@@ -146,4 +148,4 @@ TODO
146148

147149
### How about Safety?
148150

149-
We want all these features to be safe by default, and are happy to not expose some features if the gain is too small for the safety risk. As an example, Enzyme can compute the derivative with respect to a global. That's probably too niche, and could be discouraged (and unsafe) for Rust.
151+
We want all these features to be safe by default, and are happy to not expose some features if the gain is too small for the safety risk. As an example, Enzyme can compute the derivative with respect to a global. That's probably too niche, and could be discouraged (and unsafe) for Rust.

‎src/2024h2/a-mir-formality.md‎

Lines changed: 8 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -1,10 +1,12 @@
11
# Testing infra + contributors for a-mir-formality
22

3-
| Metadata | |
4-
| -------- | -------------- |
5-
| Owner(s) | @nikomatsakis |
6-
| Teams | [types] |
7-
| Status | Accepted |
3+
| Metadata | |
4+
| --- | --- |
5+
| Owner(s) | @nikomatsakis |
6+
| Teams | [types] |
7+
| Status | Accepted |
8+
| Tracking issue | [rust-lang/rust-project-goals#122] |
9+
810

911
## Summary
1012

@@ -55,4 +57,4 @@ We will require participation from at least 2 other members of T-types. Current
5557

5658
### What do I do with this space?
5759

58-
*This is a good place to elaborate on your reasoning above -- for example, why did you put the design axioms in the order that you did? It's also a good place to put the answers to any questions that come up during discussion. The expectation is that this FAQ section will grow as the goal is discussed and eventually should contain a complete summary of the points raised along the way.*
60+
*This is a good place to elaborate on your reasoning above -- for example, why did you put the design axioms in the order that you did? It's also a good place to put the answers to any questions that come up during discussion. The expectation is that this FAQ section will grow as the goal is discussed and eventually should contain a complete summary of the points raised along the way.*

‎src/2024h2/annotate-snippets.md‎

Lines changed: 8 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -1,10 +1,12 @@
11
# Use annotate-snippets for rustc diagnostic output
22

3-
| Metadata | |
4-
| -------- | -------------------- |
5-
| Owner(s) | @estebank, @Muscraft |
6-
| Teams | [compiler] |
7-
| Status | Accepted |
3+
| Metadata | |
4+
| --- | --- |
5+
| Owner(s) | @estebank, @Muscraft |
6+
| Teams | [compiler] |
7+
| Status | Accepted |
8+
| Tracking issue | [rust-lang/rust-project-goals#123] |
9+
810

911
## Summary
1012

@@ -84,4 +86,4 @@ This section defines the specific work items that are planned and who is expecte
8486

8587
*This is a good place to elaborate on your reasoning above -- for example, why did you put the design axioms in the order that you did? It's also a good place to put the answers to any questions that come up during discussion. The expectation is that this FAQ section will grow as the goal is discussed and eventually should contain a complete summary of the points raised along the way.*
8688

87-
[cargo-lints]: https://github.com/rust-lang/cargo/issues/12235
89+
[cargo-lints]: https://github.com/rust-lang/cargo/issues/12235

‎src/2024h2/async.md‎

Lines changed: 9 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -1,11 +1,13 @@
11
## Bring the Async Rust experience closer to parity with sync Rust
22

3-
| Metadata | |
4-
| ----------- | -------------------------- |
5-
| Short title | Async |
6-
| Owner(s) | @tmandry, @nikomatsakis |
7-
| Teams | [lang], [libs], [libs-api] |
8-
| Status | Flagship |
3+
| Metadata | |
4+
| --- | --- |
5+
| Short title | Async |
6+
| Owner(s) | @tmandry, @nikomatsakis |
7+
| Teams | [lang], [libs], [libs-api] |
8+
| Status | Flagship |
9+
| Tracking issue | [rust-lang/rust-project-goals#105] |
10+
911

1012
## Summary
1113

@@ -257,4 +259,4 @@ Yes, we do, and the [existing document][avd] has been very helpful in understand
257259
Keyword generics is an ambitious initiative to enable code that is "maybe async". It has generated significant controversy, with some people feeling it is necessary for Rust to scale and others judging it to be overly complex. One of the reasons to [reorganize the async WG](#reorganize-the-async-wg) is to help us come to a consensus around this point (though this topic is broader than async).
258260

259261
[MCP 727]: https://github.com/rust-lang/compiler-team/issues/727
260-
[sb]: https://smallcultfollowing.com/babysteps/blog/2023/02/01/async-trait-send-bounds-part-1-intro/
262+
[sb]: https://smallcultfollowing.com/babysteps/blog/2023/02/01/async-trait-send-bounds-part-1-intro/

‎src/2024h2/cargo-script.md‎

Lines changed: 8 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -1,10 +1,12 @@
11
# Stabilize cargo-script
22

3-
| Metadata | |
4-
| -------- | --------------- |
5-
| Owner(s) | @epage |
6-
| Teams | [cargo], [lang] |
7-
| Status | Accepted |
3+
| Metadata | |
4+
| --- | --- |
5+
| Owner(s) | @epage |
6+
| Teams | [cargo], [lang] |
7+
| Status | Accepted |
8+
| Tracking issue | [rust-lang/rust-project-goals#119] |
9+
810

911
## Summary
1012

@@ -69,4 +71,4 @@ This section defines the specific work items that are planned and who is expecte
6971
| Subgoal | Owner(s) or team(s) | Notes |
7072
| ---------------------- | ------------------------ | ----- |
7173
| Implementation | @epage | |
72-
| Stabilization decision | ![Team][] [lang] [cargo] | |
74+
| Stabilization decision | ![Team][] [lang] [cargo] | |

0 commit comments

Comments
 (0)