mirror of
https://github.com/ethereum/solidity
synced 2023-10-03 13:03:40 +00:00
Put instructions in comments.
This commit is contained in:
@@ -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.
|
||||
-->
|
||||
Reference in New Issue
Block a user