rfc-template.txt (1567B)
1 RFC SUMMARY 2 3 Free-form brief summary of the RFC's goals, 1-2 paragraphs in length. 4 5 LANGUAGE IMPLICATIONS 6 7 Enumerate proposed language changes in this section, if any. 8 9 Put "None" here if there are no language implications. 10 11 STANDARD LIBRARY IMPLICATIONS 12 13 Enumerate proposed standard library changes in this section, if any. 14 Focus on breaking changes to the standard library's API over 15 implementation details, unless implementation details are particularly 16 important. 17 18 Put "None" here if there are no standard library implications. 19 20 ECOSYSTEM IMPLICATIONS 21 22 Include considerations for the broader Hare ecosystem here, such as a 23 survey estimating how many third-party codebases will be affected and 24 how difficult it will be to implement the changes. If necessary, make a 25 plan for alleviating the impact, such as automated migration tools (e.g. 26 a sed script, or a dedicated tool for more complex migrations). 27 28 Put "None" here if there are no ecosystem implications (though in this 29 case, why is there an RFC for it?). 30 31 EXAMPLE CODE 32 33 Include in this section samples of example code as it will appear under 34 this RFC's proposed changes. This section is mandatory. 35 36 RELATED RFCS 37 38 Include a link to relevant RFCs (such as the prior version) on the 39 hare-rfc web archives, as well as a brief summary of changes from that 40 version or the reason why this RFC is relevant. 41 42 Put "None" here if there are no relevant RFCs.