[Bug]: `call()` can lead to PHP fatal error when arguments are mixed

[stloyd]

What happened?

Mixing types of parameters will lead to a fatal error.

We should either:

1. Enforce check if parameter has numeric keys and $refAlias is an integer,
2. Enforce parameters to have only string keys and $refAlias to be a string,

Option 1 still has a problem from the second point, where the order of parameters will not match the function definition, either leading to invalid results or to deprecation warnings.

How to reproduce?

call('implode', ['separator' => ',']) // fatal
call('implode', [',']) // possible deprecation (wrong parameters order)

Data required to reproduce bug locally

No response

Version

0.27

Relevant error output

In CallUserFunc.php line 50:
                                                                        
  Cannot use positional argument after named argument during unpacking

[norberttech]

The original intention of allowing for int was to be able to pass arguments by name or position.

So for example:

• ['param_name_1' => 'param_value_1', 'param_name_2' => 'param_value_2']
• ['param_value_1', 'param_value_2']

And ideally I would like to keep it this way.

However to be able to use it with positional parameter you need to do something lke this:

call(ref('column'), ['param_1, null, 'param_2'], refALias: 1]) 

So array merge would replace [1 => null] with [1 => ref('column')->eval()]

(this wasn't properly documented)