| 1 | <?php |
||
| 10 | final class AuthorizationProvider implements ServiceProviderInterface |
||
| 11 | { |
||
| 12 | /** |
||
| 13 | * @param Container $container |
||
| 14 | */ |
||
| 15 | 1 | public function register(Container $container) |
|
| 27 | |||
| 28 | /** |
||
| 29 | * @param Container $container |
||
| 30 | */ |
||
| 31 | private function registerRoleHierarchyResolver(Container $container) |
||
| 44 | } |
||
| 45 |
PHP Analyzer performs a side-effects analysis of your code. A side-effect is basically anything that might be visible after the scope of the method is left.
Let’s take a look at an example:
If we look at the
getEmail()method, we can see that it has no side-effect. Whether you call this method or not, no future calls to other methods are affected by this. As such code as the following is useless:On the hand, if we look at the
setEmail(), this method _has_ side-effects. In the following case, we could not remove the method call: