---
# Every document starts with a front matter in YAML enclosed by triple dashes.
# See https://jekyllrb.com/docs/front-matter/ to learn more about this concept.
taip: TAIP-X <X will be changed to the PR number if accepted>
title: <TAIP title>
author: <a list of the author's or authors' name(s) and/or username(s), or name(s) and email(s), e.g. (use with the parentheses or triangular brackets): FirstName LastName (@GitHubUsername), FirstName LastName <foo@bar.com>, FirstName (@GitHubUsername) and GitHubUsername (@GitHubUsername)>
discussions-to: <URL(s); if multiple, list separated by , without " or []>
status: Draft
type: <Standard | Meta | Informational>
created: <date created on, in ISO 8601 (yyyy-mm-dd) format>
updated: <date last updated, in ISO 8601 (yyyy-mm-dd) format>
requires (*optional): <TAIP number(s); if multiple, format as `[1,2]` array>
replaces (*optional): <TAIP number(s); if multiple, format as `[1,2]` array>
---
This is the suggested template for new TAIPs.
Note that an TAIP number will be assigned by an editor. When opening a pull request to submit your TAIP, please use an abbreviated title in the filename, eip-draft_title_abbrev.md.
The title should be 42 characters or less.
If you can't explain it simply, you don't understand it well enough." Provide a simplified and layman-accessible explanation of the TAIP.
A short (~200 word) description of the technical issue being addressed.
The motivation is critical for TAIP. It should clearly explain why the state of the art is inadequate to address the problem that the TAIP solves. TAIP submissions without sufficient motivation may be rejected outright.
The technical specification should describe the standard in detail. The specification should be detailed enough to allow competing, interoperable implementations.
The rationale fleshes out the specification by describing what motivated the design and why particular design decisions were made. It should describe alternate designs that were considered and related work, e.g. how the feature is supported in other languages. The rationale may also provide evidence of consensus within the community, and should discuss important objections or concerns raised during discussion.-->
All TAIPs that introduce backwards incompatibilities must include a section describing these incompatibilities and their severity. The TAIP must explain how the author proposes to deal with these incompatibilities. TAIP submissions without a sufficient backwards compatibility treatise may be rejected outright.
- TAIP-1 defines the TAIP document structure
Copyright and related rights waived via CC0.