- Abstract
- Motivation
- Technical Details
- Performance Considerations
- Impact on Existing Functionalities
- Open Questions
A general description of the RFC topic. What is the problem that this RFC is trying to address? Add a brief description of why it is necessary.
The description of some concrete use cases which have lead to the necessity of this RFC. Include as much background context which is relevant or necessary to understand the idea and design choices.
Describe the idea in appropriate detail, how it fits in the overall architecture and how it aligns with the product vision. Document in detail how the implementation of this RFC will be carried out. The size of this may vary between a few sentences to multiple standalone subsections, depending on the scope of the change/addition.
Feel free to include code samples, diagrams, and any further content which facilitates the visualization and/or comprehension of the RFC scope.
As performance is one of our core values, performance considerations should be separately described, where applicable. Any limitations, or expected significant performance degradations should be listed here.
Any impacts on existing functionality, breaking changes, or deviation from product vision should be documented here, alongside explanations why they cannot/should not be circumvented.
Any open questions that the submitter is seeking feedback for should be listed here in as much detail as possible, if applicable.