---
# System prepended metadata

title: T-spec meeting 2024-11-21
tags: [T-spec, meeting, minutes]

---

---
title: T-spec meeting 2024-11-21
tags: ["T-spec", "meeting", "minutes"]
date: 2024-11-21
discussion: https://rust-lang.zulipchat.com/#narrow/stream/399173-t-spec/topic/Meeting.202024-11-21
url: https://hackmd.io/W6yZTQWGTGyk4jrRu1zZyA
---

Attendees: Joel Marcey, Connor Horman, Eric Huss, Mara Bos, Monaidc Cat, Sid Askary, Pierre-Emmanuel Patry, TC, pnkfelix

Regrets: Niko Matsakis

Agenda

* Quick (for real this time) FLS Update - 5 minutes max
* H1 2025 Project Goal - 15 minutes
* Values and Representation - 15 minutes
* Propose no meeting next week - 2 minutes

## Quick FLS Update

Joel: Florian and I have met and are beginning the logistical process of transferring the FLS to Project. The first step is to make sure there are no legal hurdles (there shouldn't be) to transfer the copyright over to the Foundation and keep the licensing as-is.

Joel: Assuming the legal hurdles go well, then we can start the technical process of the transfer (e.g, repo) as well as communicating the transfer to the world.

Joel: Personal hope is to get this process started in earnest after the Thanksgiving Holiday in the U.S. and have most things complete by the Christmas Holiday.

Eric: Adding Ferrous FLS folks to the `t-spec` team?

Joel: Could create a transfer team or add them to the full team?

TC/Connor: Add them to the contributors team.

## H1 2025 Project Goal(s)

Joel: Josh Triplett sent out an email soliciting H1 2025 Project goals, due on 2 December. 

Joel: Niko may be sketching out an idea here, so we can be on the lookout for that.

Joel: One idea of a Project Goal is to have the FLS transferred into the Project and integrated into our specification workflow with the Reference, test annotations, etc.

Joel: Another idea of a Project Goal is to complete the test annotation work that can be utilized by both the Reference and the FLS.

Connor: Make a plan to do the FLS integration was a potential goal

Mara: A primary purpose of project goal is to write down what we need from other teams. e.g., compiler team available to review testing.

TC: In addition to that, we're essentially executing on the June plan, for which we wrote down a series of bullet points, so it may be worth recovering those and just putting those in a project goal.

Joel: Mara, did all of the H2 2024 goals have cross-team needs in them?

Mara: Here is an example: https://github.com/hexcatnl/rust-project-goals/blob/all-hands/src/2025h1/all-hands.md. For our project goal we would have a similar table to ask the compiler team to review tests, for example.

Mara: Here is another template: https://github.com/rust-lang/rust-project-goals/blob/main/src/TEMPLATE.md

TC: Niko will likely have something that is a more holisitc vision of how project-wide (or at least lang-wide) processes may integrate the specification.

## Values and Representation

<https://github.com/rust-lang/reference/pull/1664>

Connor: Discuss Eric's comment - https://github.com/rust-lang/reference/pull/1664#pullrequestreview-2416791757

Connor: Should we place the definition of types in the chapters of types where they are being defined?

TC: Eric and TC talked about this a few weeks back. It's hard to see how to combine it. There are enough differences between the types. As an organizational matter, there's duplication with what's already there.

Mara: To avoid overlap, we should have a new categorization for shared things. Give a name to the whole category. Easy for folks to write an RFC that have a well-defined "word".

Connor: Don't combine tuple and struct type chapters, but maybe their layouts can be the same.

Joel: Where do we proceed in the absence of a strong alternative?

TC: Stay with status quo.

Connor: Do we have a status quo?

Eric: Yes, the types are defined in the chapters where they are written.

Joel: What does it mean for Connor's PR if we go with status quo? Close PR and/or move words to other places?

TC: Yes, one of those two.

Connor: But where do common words for different types go?

pnkfelix: Create a new aggregate chapter for those.

## Chat

Mara Bos
Mara Bos says:
https://github.com/hexcatnl/rust-project-goals/blob/all-hands/src/2025h1/all-hands.md
 
8:13


Mara Bos says:better template: 
https://github.com/rust-lang/rust-project-goals/blob/main/src/TEMPLATE.md
 
8:16
avatar
Connor Horman
Connor Horman says:FTR, the type-layout chapter is the same layout. 
8:23
MC
Monadic Cat
Monadic Cat says:The "glossary isn't normative" distinction here seems weird to me
Seems like "just cut and paste the value representation sections to type specific chapters" 
8:41
Monadic Cat says:bye 

