Template

[dcvz]

Need/problem

Describe your use case. Give as much context as you can to help other contributors understand it well.

Motivation

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.

Detailed design

This is the bulk of the RFC. Explain the design in enough detail for maintainers
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.

Drawbacks

Why should we not do this? Please consider:

• implementation cost, both in term of code size and complexity
• the impact on usage or adoption
• integration of this feature with other existing and planned features
• cost of migrating existing projects (is it a breaking change?)
  There are tradeoffs to choosing any path. Attempt to identify them here.

Alternatives

List here the alternatives that you considered to tackle the problem and
why you ruled them out in favour of your proposed solution.

Adoption strategy

If we implement this proposal, how will existing users adopt it? Is
this a breaking change?

Unresolved questions

Optional, but suggested for first drafts. What parts of the design are still
TBD?