Closed (won't fix)
Project:
Drupal core
Version:
9.3.x-dev
Component:
other
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
4 Oct 2012 at 19:24 UTC
Updated:
14 Jul 2021 at 12:47 UTC
Jump to comment: Most recent
Comments
Comment #1
Crell commentedA lot of this looks like it exists already in PHP, just as a function with an array_ prefix.
I'm not clear on the use case. We're not doing Laravel-style routing. At first glance it works on arrays, not collection objects, which limits its usefulness to the things that PHP already has natively. I guess I just don't get it...
Comment #2
chx commentedJust looking at some of the methods, probably i didnt do enough research but map, reduce, etc exist just fine already as native php functions.
We already have a http://drupal.org/node/1794140 Typed Data API. How would this simplify / complicate / overlap / relate altogether ?
Comment #4
mathieuhelie commentedFollowing the DrupalCon New Orleans session "Rethinking Loops" I think we should reopen the issue as the arguments presented during the session are very convincing. Nesting calls to php's built-in array_* functions makes code harder to read and harder to manipulate, and the Drupal project would benefit from a collection manipulation library.
Other alternatives (mentioned during the presentation):
- \Haystack\HArray
Feel free to suggest a better one.
Comment #15
jeroentSince the repository is archived on github, I'm going to close this issue.