- Start Date: (fill me in with today's date, YYYY-MM-DD)
- Target Major Version: (1.0 / 2.0)
- Reference Issues: (fill in existing related issues, if any)
- Implementation PR: (leave this empty)
A brief explanation of the feature.
If the proposal involves a new or changed API, include a basic code example. Omit this section if it's not applicable.
Why are we doing this? What use cases does it support? What is the expected outcome?
Please focus on explaining the motivation so that if this RFC is not accepted, the motivation could be used to develop alternative solutions. In other words, enumerate the constraints you are trying to solve without coupling them too closely to the solution you have in mind.
This is the bulk of the RFC. Explain the design in enough detail for somebody familiar with xiao-Akatsuki to understand, and for somebody familiar with the implementation to implement. This should get into specifics and corner-cases, and include examples of how the feature is used. Any new terminology should be defined here.
Why should we not do this? Please consider:
- implementation cost, both in terms of code size and complexity
- whether the proposed feature can be implemented in user space
- the impact on teaching people xiao-Akatsuki
- integration of this feature with other existing and planned features
- cost of migrating existing xiao-Akatsuki applications (is it a breaking change?)
There are tradeoffs to choosing any path. Attempt to identify them here.
What other designs have been considered? What is the impact of not doing this?
If we implement this proposal, how will existing xiao-Akatsuki developers adopt it? Is this a breaking change? Can we write a method? Can we provide a runtime adapter library for the original API it replaces? How will this affect other projects in the xiao-Akatsuki ecosystem?
Optional, but suggested for first drafts. What parts of the design are still TBD?