nope, that's on purpose, to preserve bc

ok, updated to a bc layer then

why should we change something here? what's the benefit?

If you want to mix named arguments with manual indexes, you'll currently get something weird:

class Foo {
    public function __construct ($foo, $bar) {}
}

services:
    Foo:
        $bar: 'bar'
        0: 'foo'

@Foo will be instantiated as new Foo('bar', 'foo')... Imo we should either not support mixing named/indexed arguments or consider the indexes.

are you sure? there is a ksort in ResolveNamedArgumentsPass:
https://github.com/symfony/symfony/blob/master/src/Symfony/Component/DependencyInjection/Compiler/ResolveNamedArgumentsPass.php#L71

Yes I added another test case to show it.

Closing as discussed ;)