- Feature Name: (fill me in with a unique ident,
my_new_feature) - Start Date: (fill me in with today's date, YYYY-MM-DD)
- RFC PR: flybywiresim/rfcs#0000
- A32NX Issue: flybywiresim/a32nx#0000
One paragraph explanation of the feature.
Why are we doing this? What is the expected outcome?
A quick overview: explain the feature/change as if it were already implemented in the aircraft's code, and you were teaching it to another developer on the project.
Introduce new named concepts, use examples when applicable, etc.
This is the technical portion of the RFC. Explain the design in sufficient detail that:
- Its interaction with other features is clear.
- It is reasonably clear how the feature would be implemented.
- Corner cases are dissected by example.
The section should return to the examples given in the previous section, and explain more fully how the detailed proposal makes those examples work.
Why should we not do this?
- Why is this design the best in the space of possible designs?
- What other designs have been considered and what is the rationale for not choosing them?
- What is the impact of not doing this?
Any unresolved questions you may have about this feature and its possible implementation.
How this feature or change could be expanded on in future PR's and RFC's.