---
title: "EuroRust meeting agenda brainstorming"
tags: T-types
date: 2023-09-26
url: https://hackmd.io/_jGVGRrXRoef8AzbDC1NfA
---

What do we want to talk about

# SEE https://hackmd.io/cO1NJWTHTVihbE0UCWyRfg for the final doc

TODO: go through last years doc for remaining open topics https://hackmd.io/nNC_Z6nVSpW-ANkpJdSgpg?both

## Topic suggestions

- Check on [roadmap](https://blog.rust-lang.org/2023/01/20/types-announcement.html#roadmap) progress
- `-Ztrait-solver=next-coherence` stabilization, going through all decisions we have to make before that. @lcnr @compiler-errors to prepare
- `-Ztrait-solver=next` typechecking status :shrug: we'll see what will be important there
- going through the backlog of accepted, yet unstable, type system features
- `#[refine]` attribute
- do we want `types-contributors`, organizational improvements
- "where do we see Rust in 5 years" vibeck
- Polonius & borrowck
- Specification planning
- @lcnr: required steps for stabilization, use #65991 as an example
- responsibilities and purpose of the types team and the requirements for team members.
- a-mir-formality *something* -- roadmap, explanations
- lazy normalization check
- any goals and region checking

### Organizational

* Retrospective / Organizational overview
* Here are some suggestions for things that could change
* Types contributors
* Stabilization
* Retrospective

## Rough outline

@lcnr: I think we should keep at least half of that day open to allow us to use it in case something comes up during the meetup itself or we need more time to discuss other topics.

## mir-formality

jackh726: useful to have a roadmap + what parts we expect to require novelty, where things diverge from rustc

## what do we want to leave the meetup with?

* what is blocking next-coherence, path to stabilization for that
* what is blocking TAIT, path to stabilization for that
* what is blocking polonius, path to stabilization for that
* alignment on mir-formality roadmap
* stabilization process