Finding the ... operator for argument unpacking
Nobody has claimed this yet.
- Dominant language
- XML
- Stars
- 596
- Forks
- 890
- Avg merge
- 1d 15h
- Merged PRs (30d)
- 55
Description
Hello everyone it's the first time I try to contribute to the php documentation.
I find the ... operator for argument unpacking very useful.
I found it only today using a topic on stackoverflow here where we can find a comprehensive example and a link to the documentation page from function arguments documentation page here
I also found another page here on php doc page that was probably a proposal at first, right? And another from the new features of php 5.6 here.
Well, in this proposal and the new features for 5.6, the ... token was called an operator.
My question is : is it an operator ?
And if it is one, should it be listed inside the operators precedence page ?
The problem here is that I find it very difficult for anyone to find this ... construct because it is not documented as an operator in this page, and it is not searchable as is because it is made of symbols - neither on php.net nor on any search engine that I know of.
Do you think you could add it to the operators precedence page ?
It is my humble opinion that it would ensure a larger audience for this topic, what do you think?
I hope I didn't intrude too much. And I respectfully ask that you forgive me if my English lacks refinement... well I'm french.
Thank you for reading my prose so far.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by comparing the function arguments documentation, the operators precedence page, the PHP 5.6 new-features entry, and the argument unpacking RFC linked in the issue. Check how the ... construct is classified and whether adding it to the precedence page is technically appropriate. Done means reaching a documented decision and updating the relevant PHP manual page if the change is accepted.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100