Why force using named arguments in BoundMethod? bug or intended behaviour?

[Tamce]

Recently I'm building a project with illuminate/container separately.
But I found something frustrating.

Before 7.x:

$container->instance(SomeClass::class, $o);
$container->call('foo', [1]);

function foo(SomeClass $dependency, $bar) {
    // $bar is 1
}

Everything is fine, but after 7.x, I got an Uncaught Illuminate\Contracts\Container\BindingResolutionException in argument #1 ($bar)

reviewing the code, it is caused by [BoundMethod.php L178](https://github.com/illuminate/container/blob/master/BoundMethod.php#L178}

And the problem is that argument $bar's name could not be found at the input argument array. The input array should be ['bar' => 1] instead of [1].

It is very inconvenient. So I wonder why this feature was introduced.
Best regards.