---
# System prepended metadata

title: T-spec meeting 2024-08-29
tags: [T-spec, meeting, minutes]

---

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

Attendees: Joel Marcey, Connor Horman, TC, Eric Huss, Urgau, Pierre-Emmanuel Patry, Nandini Sharma, Monadic Cat, pnkfelix

Minutes: Joel Marcey

Agenda:

* Reference translation progress
* Next steps for reference translation

## Reference Translation Progress

Issue tracker: https://github.com/rust-lang/reference/pull/1561

Connor: A little bit behind, but still planned to be finished by the end of the week. In a single omnibus PR.

TC: Heads-up that we merged a PR that prevents the anchors from rule names from colliding with those of section headers:

https://github.com/rust-lang/reference/pull/1593

Joel: Expectation is that by the end of the week that all reference chapters will have been translated with ids?

Connor: Yes, save for a few exceptions. ABI. Glossary. Anything that doesn't contain normative content. 

Joel: Is the idea to keep the exceptions as they are?

Connor: The idea for the exceptions for those are to give them normative content.

Tracking issue:

https://github.com/rust-lang/reference/issues/1561

Connor: Rest of the work will be in omnibus PRs.

Eric: Would prefer single chapter PRs.

Connor: Will submit one omnibus that has started (that contains 7 chapters), but the rest will be single chapters.

## Next Steps for Reference Translation

Connor: The work to adding the spec identifiers to the reference is nearly complete. What do we do next?

Connor: Has noticed there is not a lot of consistency throughout the reference. Syntax, intro, result, behavior is preferred formula, but not everything could be neatly separated out like that.

Connor: The next step should be to make everything consistent in how it is described.

TC: The next step may be to focus on testing.  A way to tie together the UI and other tests with Reference chapters.  This is in the critical path for the Reference to be an FLS replacement in the safety critical space.

Connor: With the inline tests, it may be easier to do both consistency work and adding tests.

Eric: Fine with doing things in parallel. Proposed adding annotations to Rust so that rules can be tied to different tests - this proposal is coming.

pnkfelix: My instinct: I would not want to try to fine tune the identifiers into their final idealized form before doing the work on tests. I think it would be better to anticipate the eventual need for identifiers to be able to *change* as things evolve, and the associated need to metadata tracking such changes.

Joel: Tests may not provide 100% correctness within the reference at first, but that's ok. Getting the test structure in place is important.

TC: It would be good to identify areas where the reference doesn't cover a topic and pull data in from the FLS and other sources.

TC: The goal is to be strictly better than the FLS.

## Next priorities

TC: Concretely, the next priorities are:

- Finishing reformatting, addressing any review comments, and merging those.
- Identify areas that the FLS covers that we do not.
- Pull in and adapt or author content in those areas.
- Associate tests with Reference chapters.
  - Chapter granularity is OK as a start.

ehuss, Joel, pnkfelix: +1.

Joel: What is the timeframe here for the test additions, plus any additional ancillary work?

Connor: Unsure about specific timeframe here - specifically as to inline tests, but expect a substantial amount could be done by end of September.

## C-unwind PR

https://github.com/rust-lang/reference/pull/1226/
