aboutsummaryrefslogtreecommitdiffstats
path: root/.github/ISSUE_TEMPLATE/feature_request.md
diff options
context:
space:
mode:
Diffstat (limited to '.github/ISSUE_TEMPLATE/feature_request.md')
-rw-r--r--.github/ISSUE_TEMPLATE/feature_request.md12
1 files changed, 11 insertions, 1 deletions
diff --git a/.github/ISSUE_TEMPLATE/feature_request.md b/.github/ISSUE_TEMPLATE/feature_request.md
index 6b98fb99..6702b62c 100644
--- a/.github/ISSUE_TEMPLATE/feature_request.md
+++ b/.github/ISSUE_TEMPLATE/feature_request.md
@@ -3,7 +3,7 @@ name: Feature Request
about: Solidity language or infrastructure feature requests.
---
-## Prerequisites
+<!--## Prerequisites
- First, many thanks for taking part in the community. We really appreciate that.
- We realize there is a lot of data requested here. We ask only that you do your best to provide as much information as possible so we can better help you.
@@ -14,24 +14,34 @@ about: Solidity language or infrastructure feature requests.
*Delete the above section and the instructions in the sections below before submitting*
+-->
+
## Abstract
+<!--
Please describe by example what problem you see in the current Solidity language
and reason about it.
+-->
## Motivation
+<!--
In this section you describe how you propose to address the problem you described earlier,
including by giving one or more exemplary source code snippets for demonstration.
+-->
## Specification
+<!--
The technical specification should describe the syntax and semantics of any new feature. The
specification should be detailed enough to allow any developer to implement the functionality.
+-->
## Backwards Compatibility
+<!--
All language changes that introduce backwards incompatibilities must include a section describing
these incompatibilities and their severity.
Please describe how you propose to deal with these incompatibilities.
+--> \ No newline at end of file