Pluck Property on collection list about collections

[malarzm]

I'm 👎 as passing a property name doesn't tell us how to get a property out of an object (so we'll need to check public access, getter, reflection). Also tooling won't be able to find usages of a property/method as it's hidden behind "magical" access.

[yassinechabli]

i see that there is an accurate cases that can be handled.
The first easy one
When handling a collection of object that has the getter of the property in question => easy to get the property value.
The second case
if the object class has only __get method => the function pluck will handle a lot of cases .

In general ,I think using reflection could resolve the problem in all cases .

i'm a wrong ?

[someniatko]

IMO an abstract collection should not depend on internals of its underlying elements.

[lcobucci]

Agreed, this isn't a fit for this library since it involves object introspection and might potentially break encapsulation.

I think that the benefits are very limited, so will close this as "won't fix".