Design meeting: Field Projections via Virtual Places #363
Description
Summary
It's time to talk about field projections again! We've made lots of progress since the previous meeting #335 and our proposal is getting more fleshed out each week.
It still is a bit early to have this meeting in January (and February probably too), but I wanted to already put this on people's radar. I see two possible approaches for conducting the meeting, depending on how the next couple weeks of our design go:
- Explain the current proposal in a new document to the rest of t-lang and get feedback on the direction, without having everything fleshed out.
- Finish a draft of the RFC(s) and read it in the meeting, with the intention of posting them a few days later.
Option 1 would be when we still have some fundamental things to iron out and/or we still have difficult decisions to make. Option 2 makes more sense, when writing the explanatory document would be equivalent to writing the RFC. This would be the case, when we have not only good justification for our design decisions, but also thought about many more details (such as "how do we implement this?" and "how do we teach this?").
Background reading
- Document: to be written
- The updates in the goal issue are very extensive and should give an overview of the current state: Design a language feature to solve Field Projections rust-project-goals#390
About this issue
This issue corresponds to a lang-team design meeting proposal. It corresponds to a possible topic of discussion that may be scheduled for deeper discussion during one of our design meetings.