Feature: caching

[viktorprogger]

We can introduce dependecy caching in order to make container faster. I'd like to see a decision that will result into some php files with methods like these:

public function getSomeDependency(ContainerInterface $container)
{
    return new SomeDependency($container->get('anotherDependency'));
}

public function getAnotherDependency(ContainerInterface $container)
{
    return new AnotherDependency();
}

[samdark]

That's good and bad at the same time. Good because yes, likely it would be more performant. Bad because you're executing not what you've actually written so debugging becomes quite weird experience.

[armpogart]

Maybe it's better to have a way to generate compiled container for production use-case and document it the way PHP-DI and Symfony do it.

[samdark]

@armpogart as I've mentioned, it's both good an bad. Need to check if performance gain worth the trouble.

[viktorprogger]

Some time passed... Now I think the best way to increase performance by dependency caching is either RoadRunner/Swoole/etc., or php preloading usage. Everything will be created just once :)

[samdark]

Yeah. That's the way to go. I think we can close this issue. Container reset is a separate one.