[5.1] Added cached compile and service path methods to the Application interface

[proshanto]

Fixes #8229 and requested by @GrahamCampbell

[jonathanpmartins]

@taylorotwell @GrahamCampbell @proshanto, I think its not completely resolved. I have the same problem that @martinssipenko have. In this issue: laravel/lumen-framework#137

[GrahamCampbell]

Yes, we know...

[GrahamCampbell]

Lumen 5.1 is NOT meant to be used yet.

[jonathanpmartins]

Only testing... no production!

[GrahamCampbell]

Same goes there really.

[jonathanpmartins]

@taylorotwell @GrahamCampbell Sorry... try it later on!

[proshanto]

@jonathanpmartins Application contract is not perfect. There are lots of things to be done. Laravel right now is tightly coupled to the foundation implementation.

[GrahamCampbell]

Not really. All we need to do is change our contracts so that they extend array access.

[franzliedke]

Nah, there are still quite a lot other places where methods are used that aren't in the contract. Take a look at some of the bootstrapper classes, for example.

[proshanto]

@franzliedke Yeah from some artisan commands too.

[GrahamCampbell]

I'm sure Taylor would accept PRs to 5.2 to improve this provided they're not adding a massive load of methods to the contracts. NB getter/setter stuff won't get accepted to contracts.

[proshanto]

👍