rfc:alternative-closure-use-syntax
Differences
This shows you the differences between two versions of the page.
Next revisionBoth sides next revision | |||
rfc:alternative-closure-use-syntax [2019/06/15 21:44] – created wesnetmo | rfc:alternative-closure-use-syntax [2019/06/15 21:47] – wesnetmo | ||
---|---|---|---|
Line 10: | Line 10: | ||
PHP users often say that they find defining the lexical-scope imports cumbersome, because | PHP users often say that they find defining the lexical-scope imports cumbersome, because | ||
- | they hate writing the variables explicitly. My (updated) opinion on the matter is that | + | they hate writing the variables explicitly. |
- | what's actually annoying is not having to write the variable names, but the syntax | + | |
- | with which the imports are defined. In ES we are forced to declare variables and we don't | + | My (updated) opinion on the matter is that what's actually annoying is not having to write |
- | find it annoying; in PHP we don't have to declare variables, but we are required to | + | the variable names, but the syntax with which the imports are defined. |
- | specify which one we want to import in '' | + | |
- | the syntax. | + | In ES we are forced to declare variables and we don't find it annoying; in PHP we don't |
+ | have to declare variables, but we are required to specify which one we want to import in | ||
+ | '' | ||
+ | but irksome in PHP. | ||
Specifically, | Specifically, | ||
- | Whitespace, parentheses, | + | Whitespace, parentheses, |
middle of the signature, it is very invasive, visually, as it separates the arguments from | middle of the signature, it is very invasive, visually, as it separates the arguments from | ||
the return information: | the return information: |
rfc/alternative-closure-use-syntax.txt · Last modified: 2019/06/16 12:03 by wesnetmo