As default behavior it makes sense, but it should be possible to explicitly invoke the behavior using arguments and I'm not sure how the change could be squeezed into the function. NULL as the $index_key?

Anyway, the workaround is trivial:
  array_combine(array_keys($items), array_column($items, "id"))

I always saw PHP's arrays as a Swiss army knife for data manipulation. If you say this would be difficult to implement or would result in less than optimal performance I refer entirely to your judgment.
The only disadvantage I see to the workaround is the performance. Calling 3 functions is clearly slower than using just one.

That said, your point is valid and this request was just a suggestion.

I guess you even meant:

Expected result:
----------------
array(4) { [1]=> int(1) [2]=> int(4) [3]=> int(9) ["four"]=> int(16) }

(i.e. keep all keys, even numeric)

and I agree with you! (and a quick Web search shows we're not alone...)

---

@requinix: I see at least 2 ways:

  1. Add a `bool $preserve_keys = false` parameter (like array_slice)
that would at least enable us to use
    array_column($items, "id", null, true)

  2. Change the default behavior (consistent with array_map)
and just use
    array_values(array_column($items, "id"))
if you really want to lose the keys


PS: see also Request #66435