---
# System prepended metadata

title: T-spec meeting 2025-01-16
tags: [T-spec, meeting, minutes]

---

---
title: T-spec meeting 2025-01-16
tags: ["T-spec", "meeting", "minutes"]
date: 2025-01-16
discussion: https://rust-lang.zulipchat.com/#narrow/stream/399173-t-spec/topic/Meeting.202025-01-16
url: https://hackmd.io/CJjYAH4SQ1K4eXY_p48Mpg
---

Attendees: Joel Marcey, Eric Huss, TC, Pierre-Emmanuel Patry, Niko Matsakis, Monadic Cat, Sid Askary

Regrets:
- Connor Horman
- Mara Bos

Agenda

- 2025H1 Spec-related Project Goal Alignment
- T-Spec tagged GitHub Issues for Reference

## Project Goal Alignment

There are two proposed specification related Rust Project Goals for 2025H1: FLS integration and specification testing.

There are other goals that may require `t-spec` input in some manner, particularly around stabilization.

Joel: We should make sure that those goal are actually how we want them because they are public.

Niko: Support TC's opinion, goals are not only external communication but a way to decided internally what we should do over the next 6 months.

Eric: Stabilization Process. For other goals, where would the spec team be involved in documenting stabilzing features.

Niko: Goal is not to stabilize but prepare stabilization, there has been a lot of discussions surrounding stabilization processes lately

TC: Macro rules, attributes & derives should be described in the reference.

TC suggested that the template might also include other common team asks, like style team, rust-analyzer, etc.

Niko: Average contributor cannot author edits.

Joel: Who is responsible for stabilized feature documentation/reference edits/wording?

Eric: Depends. Some stabilization goal owners could write the words; others may need help.

Niko: reviewing the list of things for which spec edits might be good

Process note:

* we should add "submit first draft of spec" to the metadata
    * assign a spec reviewer to do the rest of the work
    * liaison should not need to be content expert
    * members of the spec team:
        * m-ou-se, ehuss, traviscross, nikomatsakis, JoelMarcey
    * and spec team should check "who will be authoring it"
* stabilization requested
    * [Return type notation](https://rust-lang.github.io/rust-project-goals/2025h1/async.html#ownership-and-team-asks)
        * our team will review
        * complex but driven by errs/tmandry/nikomatsakis
    * [Implement restrictions, prepare for stabilization](https://rust-lang.github.io/rust-project-goals/2025h1/restrictions.html#ownership-and-team-asks)
        * our team will review -- seems straightforward [rfc 3323](https://github.com/rust-lang/rfcs/pull/3323)
    * [macro_rules! attributes](https://rust-lang.github.io/rust-project-goals/2025h1/macro-improvements.html#ownership-and-team-asks) and friends
    * trait aliases --
        * not listed, niko thinks it's important, had half a mind to propose
        * our team would review
        * complex but driven by errs/tmandry/nikomatsakis
* stabilization not requested
    * [const traits](https://rust-lang.github.io/rust-project-goals/2025h1/const-trait.html#ownership-and-team-asks)
        * oli can author
        * team can review
    * [unsafe fields](https://rust-lang.github.io/rust-project-goals/2025h1/unsafe-fields.html#ownership-and-team-asks)
        * jswrenn can author
        * team can review
    * [pin reborrowing](https://rust-lang.github.io/rust-project-goals/2025h1/async.html#ownership-and-team-asks)
        * eholk could author
        * team can review

### Integrate the FLS into the Project

https://rust-lang.github.io/rust-project-goals/2025h1/spec-fls-integration.html

Make the goal more specific - Publish first version of the FLS within the Rust Project

This means the FLS has been integrated with tooling and publishing mechanisms like other "books" of the Project.

Niko updated the project goal real time to reflect this change in goal direction.

### Specification Test Suite

https://rust-lang.github.io/rust-project-goals/2025h1/spec-testing.html

TC: Delete this goal? We may not actually be aligned on this as a priority.

Joel: Should we wait for Connor so that he can defend it?

Eric: What does it mean to have a goal? Connor can continue to work on this without it being a goal.

Niko: Removing goal does not mean Connor can't do it. But we don't have alignment (moral support) for it to work.

## Reference: T-Spec GitHub Issues

https://github.com/rust-lang/reference/issues?q=label%3A%22T-spec%22+is%3Aopen

## Chat

Joel Marcey (Rust Foundation) says:
https://github.com/rust-lang/rust-project-goals/pull/230

Joel Marcey (Rust Foundation) says:
https://rust-lang.github.io/rust-project-goals/2025h1/goals.html

Niko Matsakis says:
https://github.com/rust-lang/rust-project-goals/pull/230
