Fix handling of PHP 7 Throwables during resolving #545
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In PHP 7, it is possible to throw something that doesn't inherit the Exception class. The most common example is that type-checking now causes a TypeError to be thrown. PHP-DI did not catch this type of error, and leaves the entry dangling as "being resolved". If the service is requested again after this happens, a "Circular dependency detected while trying to resolve entry" exception is thrown by Container even though there is no circular dependency.
The solution uses a finally block instead of catch(Exception) to ensure all possible Throwables are handled properly. This also removes the need to re-throw the exception.
Minimal test case for this behavior: