T-spec meeting 2024-08-22

--- title: T-spec meeting 2024-08-22 tags: ["T-spec", "meeting", "minutes"] date: 2024-08-22 discussion: https://rust-lang.zulipchat.com/#narrow/stream/399173-t-spec/topic/Meeting.202024-08-22 url: https://hackmd.io/pA5DrOWDTT-D7y5qTlJ7Ow --- Attendees: Joel Marcey, Connor Horman, Mara Bos, Eric Huss, Pierre-Emmanuel Patry Minutes: Joel Marcey Agenda: * Last few weeks progress check * Identifier Addition Progress [#1561](https://github.com/rust-lang/reference/issues/1561) * Paragraph Identifiers [#1573](https://github.com/rust-lang/reference/issues/1573) * Standard library docs duplication * Test suite rule annotations ## Last few weeks progress No meetings the last two weeks. Progress is given in #1561. ## Identifier Addition Progress This has been the primary work item over the last couple of works. Generally overall positive vibes on this work. Just a few comments from TC, that should be readily resolved. Eric: Identifiers looking good. But bigger concern lies in the technical reviews of all these reference chapters (e.g. panics) Connor: Have been reviewing technical content in area of expertise as identifiers have been added. Connor: Where is the identifer "crate" anchored too? Eric: Comes from the glossary. Will try to think of some solution on fixing this. Connor: A few cases where the identifier is the same as the chapter name. Connor: Should be able to finish the identifiers by the end of the month. ## Paragraph Identifiers Status Connor, Eric: Make the identifiers unique, but for now they are not stable but will be. Eric: Will comment on the issue. ## Standard Library Docs Duplication Should we duplicate the standard libarary documentation within the specification? https://doc.rust-lang.org/std/primitive.fn.html https://doc.rust-lang.org/stable/std/ptr/index.html as an example. Mara: Some of the documentation is quite long, and some of the documentation could go in many places and not obvious all of it should be in the standard library. Mara: Duplication is fine, and standard library could provide additional context with examples, gotchas, etc. Connor: The specification should contain formalizations of the standard library. Mara: There are quite a few language level items in the standard library docs that could be moved into the specification. Joel: Will the spec and standard library documentation be complementary, avoiding much duplication? Mara: Spec and standard library will be complementary, with some duplication, but will achieve different goals. Joel: Agree Agreement to move forward with the "duplication" option, adding standard library things to the spec, possibly moving some items from the standard library over, but still have deep standard library documentation as well. ## Test Suite Rule Annotations Eric: Adding annotations to the Rust test suite rule identifiers and collect those to link to tests that showcase certain rules. Eric: Beginning the process with a major change proposal with the compiler team to see if they are ok with the proposal.