---
# System prepended metadata

title: Planning meeting 2023-02-08
tags: [planning-meeting]

---

---
title: Planning meeting 2023-02-08
tags: planning-meeting
---

# T-lang planning meeting agenda

* Meeting date: 2023-02-08

## Attendance

* Team members: Niko, Josh, Tyler, Scott, Felix
* Others: Mark

## Meeting roles

* Action item scribe:
* Note-taker:

## Proposed meetings

- "Language design principles" [lang-team#189](https://github.com/rust-lang/lang-team/issues/189)
    - authors: Niko, Josh
    - would have to be late March to have a chance of getting done
- "Design decisions around the `#[expect]` attribute" [lang-team#191](https://github.com/rust-lang/lang-team/issues/191)
    - we don't know if xFrednet is available or interested in authoring a doc
    - nobody else has time to write it
- "discuss/resolve `fn { mod { (use) super::...; } }` and its interaction with derive patterns" [lang-team#193](https://github.com/rust-lang/lang-team/issues/193)
    - Tentatively February 15 - compiler team considers this urgent
- "Design Meeting: Field Projection" [lang-team#194](https://github.com/rust-lang/lang-team/issues/194)
    - y86-dev proposed to discuss it, would prefer March or later
    - async wg did a review that raised questions, have those answers been incorporated? unclear. [notes](https://hackmd.io/79TICQb0SPWCIcz02IiWaA?view)
    - at minimum, a couple of starting questions to help us focus the discussion
- "Post-monomorphization errors" [lang-team#195](https://github.com/rust-lang/lang-team/issues/195)
    - author: tmandry
    - try to schedule this for sure
    - maybe schedule two dates :) 
- "Interface between opsem and lang team" [lang-team#196](https://github.com/rust-lang/lang-team/issues/196)
    - authors: jakob degen, ralf, pnkfelix
- "Temporary lifetimes" [lang-team#197](https://github.com/rust-lang/lang-team/issues/197)
    - authors: BN (aka [b-naber](https://github.com/b-naber)), oli... niko?
    - going in:
        - description of the problems
        - clear description of how an edition-related change could work to address them
            - ideally: we'd describe how to transform existing programs to preserve semantics unambiguously
    - goal:
        - shared understanding of problem space
        - agreement about which of the problems are most important to fix
        - ruling out or endorsing some possibilities

Other edition related things:

* IDE-related stuff or stuff that would drive compilation time improvements

## Dates to plan for

* Feb 15: Discuss/resolve `fn { mod { (use) super::...; } }` and its interaction with derive patterns [lang-team#193](https://github.com/rust-lang/lang-team/issues/193)
    * tmandry unavailable
* Feb 22: Post-monomorphization errors [lang-team#195](https://github.com/rust-lang/lang-team/issues/195)
    * pnkfelix unavailable
* Mar 1: "Interface between opsem and lang team" [lang-team#196](https://github.com/rust-lang/lang-team/issues/196)
    * reschedule if it doesn't work for jakob
    * potentially swap with lang-team#197 on March first if that has better mutual timing
* Mar 8: Design decisions around the `#[expect]` attribute [lang-team#191](https://github.com/rust-lang/lang-team/issues/191)
    * nikomatsakis unavailable
    * need to make sure xFrednet can be ready for that date
* Mar 15: Temporary lifetimes [lang-team#197](https://github.com/rust-lang/lang-team/issues/197)
* Mar 22: Language design principles [lang-team#189](https://github.com/rust-lang/lang-team/issues/189) 
* Mar 29: "Design Meeting: Field Projection" [lang-team#194](https://github.com/rust-lang/lang-team/issues/194)
        * 
