|
1 | 1 | --- |
2 | 2 | name: Feature Request |
3 | 3 | about: Solidity language or infrastructure feature requests. |
| 4 | +labels: ["feature"] |
4 | 5 | --- |
5 | 6 |
|
6 | 7 | <!--## Prerequisites |
7 | 8 |
|
8 | 9 | - First, many thanks for taking part in the community. We really appreciate that. |
9 | 10 | - 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. |
10 | 11 | - Support questions are better asked in one of the following locations: |
11 | | - - [Solidity chat](https://gitter.im/ethereum/solidity) |
12 | | - - [Stack Overflow](https://ethereum.stackexchange.com/) |
| 12 | + - [Solidity chat](https://gitter.im/ethereum/solidity) |
| 13 | + - [Stack Overflow](https://ethereum.stackexchange.com/) |
13 | 14 | - Ensure the issue isn't already reported (check `feature` and `language design` labels). |
14 | 15 |
|
15 | 16 | *Delete the above section and the instructions in the sections below before submitting* |
16 | | -
|
17 | 17 | --> |
18 | 18 |
|
19 | 19 | ## Abstract |
20 | 20 |
|
21 | | -<!-- |
22 | | -Please describe by example what problem you see in the current Solidity language |
23 | | -and reason about it. |
24 | | ---> |
| 21 | +<!--Please describe by example what problem you see in the current Solidity language and reason about it.--> |
25 | 22 |
|
26 | 23 | ## Motivation |
27 | 24 |
|
28 | | -<!-- |
29 | | -In this section you describe how you propose to address the problem you described earlier, |
30 | | -including by giving one or more exemplary source code snippets for demonstration. |
31 | | ---> |
| 25 | +<!--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.--> |
32 | 26 |
|
33 | 27 | ## Specification |
34 | 28 |
|
35 | | -<!-- |
36 | | -The technical specification should describe the syntax and semantics of any new feature. The |
37 | | -specification should be detailed enough to allow any developer to implement the functionality. |
38 | | ---> |
| 29 | +<!--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.--> |
39 | 30 |
|
40 | 31 | ## Backwards Compatibility |
41 | 32 |
|
42 | 33 | <!-- |
43 | | -All language changes that introduce backwards incompatibilities must include a section describing |
44 | | -these incompatibilities and their severity. |
| 34 | +All language changes that introduce backwards incompatibilities must include a section describing these incompatibilities and their severity. |
45 | 35 |
|
46 | 36 | Please describe how you propose to deal with these incompatibilities. |
47 | | ---> |
| 37 | +--> |
0 commit comments