LEP template¶
LEP |
LEPxxxx |
Author(s) |
(co)author name(s) |
Reviewer(s) |
reviewer(s) name(s) |
Status |
Draft |
Type |
Standard (S) or Informational (I) or Governance (G) |
Created |
date |
Finalized |
date |
Abstract¶
[A short (~200 word) description of the technical issue being addressed.]
Motivation¶
[Clearly explain why the existing language specification is inadequate to address the problem that the LEP solves.]
Rationale¶
[Describe why particular design decisions were made.]
Specification¶
[Describe the syntax and semantics of any new language feature.]
Backwards Compatibility¶
[Describe potential impact and severity on pre-existing code.]
Security Implications (Optional)¶
[How could a malicious user take advantage of this new feature?]
How to Teach This (Optional)¶
[How to teach users, new and experienced, how to apply the LEP to their work.]
Proof of concept¶
[Clear and concise example that shows that the implementation actually works.]
Rejected Ideas¶
[Why certain ideas that were brought while discussing this LEP were not ultimately pursued.]
Open Issues¶
[Any points that are still being decided/discussed.]
References¶
[A collection of URLs used as references through the LEP.]
Copyright¶
Copyright is owned by Ratio Computer Aided Systems Engineering B.V.