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:array_change_keys [2016/05/31 02:16] – Emphasize that no new quirks are being added colinodell | rfc:array_change_keys [2017/01/08 13:45] – colinodell |
---|
==== Function Name ==== | ==== Function Name ==== |
| |
PHP already has an ''array_change_key_case()'' function, so sharing a common root name (''array_change_key'') seems like a logic choice. | PHP already has an ''array_change_key_case()'' function, so sharing a common root name (''array_change_key'') seems like a logical choice. |
| |
Other function which deal with multiple keys (like ''array_keys'' and ''array_fill_keys'') are pluralized, so we're using that same convention here. | Other functions which deal with multiple keys (like ''array_keys'' and ''array_fill_keys'') are pluralized, so we're using that same convention here. |
| |
===== Discussion ===== | ===== Discussion ===== |
===== Future Scope ===== | ===== Future Scope ===== |
| |
Returning ''__toString()''able objects from the callback is not supported by this RFC. This matches the behavior of other functions like ''array_flip()'' and ''array_fill_keys()''. If such functionality is desired, a separate RFC could be created to add this functionality to all similar functions. | Other ''array_'' functions do not support certain features like using ''__toString()'' for keys or supporting ''Traversable'' objects like iterators, so support for them is not being proposed here either. If such functionality is desired, a separate RFC could be created to add this functionality to all similar functions. |
| |
===== Proposed Voting Choices ===== | ===== Proposed Voting Choices ===== |