rfc:group_use_declarations
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
rfc:group_use_declarations [2015/02/13 17:41] – Use DokuWiki '' syntax ajf | rfc:group_use_declarations [2015/02/25 20:41] – close voting marcio | ||
---|---|---|---|
Line 24: | Line 24: | ||
===== Proposal ===== | ===== Proposal ===== | ||
- | Group use declarations are just **syntactic sugar** | + | Group use declarations are used to cut verbosity when importing multiple entities from a common namespace. Using common PHP library examples, the following use declarations are equivalents: |
<code php> | <code php> | ||
Line 125: | Line 125: | ||
use Symfony\Component\Console\Question\{ | use Symfony\Component\Console\Question\{ | ||
ConfirmationQuestion, | ConfirmationQuestion, | ||
- | ChoiceQuestion as Choice; | + | ChoiceQuestion as Choice, |
+ | + | ||
Question, | Question, | ||
Line 153: | Line 153: | ||
* The search for literal full qualified namespaces can become less straightforward. | * The search for literal full qualified namespaces can become less straightforward. | ||
- | ===== About The Syntax Choice | + | ==== About The Syntax Choice ==== |
The syntax chosen is inline with the current [[http:// | The syntax chosen is inline with the current [[http:// | ||
Line 173: | Line 173: | ||
This shall be addressed on voting phase: should a trailing " | This shall be addressed on voting phase: should a trailing " | ||
- | |||
- | ===== Backward Incompatible Changes ===== | ||
- | There is no BC breaks with current implementation or feature concepts. | ||
===== Proposed PHP Version(s) ===== | ===== Proposed PHP Version(s) ===== | ||
Line 181: | Line 178: | ||
===== RFC Impact ===== | ===== RFC Impact ===== | ||
+ | |||
+ | === On Functional Programming / Autoloading === | ||
+ | |||
+ | Group use declarations is also very helpful for the PHP user base more fond to the **functional** programming paradigms. This RFC would be especially important if PHP finally gets **function autoloading**. | ||
+ | |||
+ | Currently, sets of independent functions have to be implemented as static classes. But with function autoloading, | ||
+ | |||
+ | <code php> | ||
+ | // Current use syntax: | ||
+ | |||
+ | use function iter\range; | ||
+ | use function iter\map; | ||
+ | use function iter\filter; | ||
+ | use function iter\apply; | ||
+ | use function iter\reduce; | ||
+ | use function iter\fn\operator; | ||
+ | |||
+ | // Proposed syntax: | ||
+ | |||
+ | use function iter\{ range, map, filter, apply, reduce, fn\operator }; | ||
+ | |||
+ | </ | ||
=== On Backward Compatibility === | === On Backward Compatibility === | ||
Line 193: | Line 212: | ||
* [[http:// | * [[http:// | ||
* [[http:// | * [[http:// | ||
- | * [[https:// | + | * [[https:// |
===== Votes ===== | ===== Votes ===== | ||
As this is a language change, this RFC requires a 2/3 majority of Yes votes (with or without trailing " | As this is a language change, this RFC requires a 2/3 majority of Yes votes (with or without trailing " | ||
- | <doodle title=" | + | <doodle title=" |
* Yes - **with** a trailing " | * Yes - **with** a trailing " | ||
* Yes - **without** a trailing " | * Yes - **without** a trailing " | ||
* No | * No | ||
</ | </ | ||
+ | |||
+ | ===== Discussion in a Nutshell ===== | ||
+ | |||
+ | In case you missed the discussion. This section lists the common counter points towards this RFC and how they were replied by the RFC author and supporters on mailing lists and media: | ||
+ | |||
+ | ==== My IDE already does the imports for me and folds the namespaces so I don't need this feature ==== | ||
+ | |||
+ | We should create **usable languages by design** rather than **languages only usable by tooling**. Tooling can be very important | ||
+ | but the moment you notice a stack of tools is needed to have a reasonable experience and readability with a programming language then something needs to be improved. | ||
+ | |||
+ | A programming language should be able stand on its own and not require IDE assistance for reasonable use. That's what this RFC does, it brings a very common feature already available in many languages employing some kind of namespacing. | ||
+ | |||
+ | ==== The RFC encourages violation of the the SRP and other best practices ==== | ||
+ | |||
+ | This is **not true**. Nikita already wrote a great response to this on the official PHP mailing list. Beware of the slay of good argumentation ahead: http:// | ||
+ | |||
+ | ==== We should have "first class packages" | ||
+ | |||
+ | This is painfully illogic. Group use declarations and "first class packages" | ||
+ | |||
+ | Doing so **prior** to a major PHP7 **release** is, in fact, the **best hour** to **approve** this RFC. | ||
+ | |||
+ | ==== We should go for Python' | ||
+ | |||
+ | I doubt Python syntax will ever be proposed for PHP because it would require the the **from** keyword to be reserved, hence one of the reasons it was discarded during research and discussion. Other reason is that the glob brace syntax is more tailored for PHP and it is a [[https:// | ||
+ | |||
===== Patches and Tests ===== | ===== Patches and Tests ===== | ||
Line 227: | Line 272: | ||
- NikiC for providing accurate information about the PHP implementation. | - NikiC for providing accurate information about the PHP implementation. | ||
- All people on http:// | - All people on http:// | ||
+ |
rfc/group_use_declarations.txt · Last modified: 2017/09/22 13:28 by 127.0.0.1