and let?s assume the following content of Bar.php:
// Bar.phpnamespaceOtherDir;useSomeDir\Foo;// This now conflicts the class OtherDir\Foo
If both files OtherDir/Foo.php and SomeDir/Foo.php are loaded in the
same runtime, you will see a PHP error such as the following:
PHP Fatal error: Cannot use SomeDir\Foo as Foo because the name is already in use in OtherDir/Foo.php
However, as OtherDir/Foo.php does not necessarily have to be loaded and the
error is only triggered if it is loaded before OtherDir/Bar.php, this problem
might go unnoticed for a while. In order to prevent this error from surfacing,
you must import the namespace with a different alias:
// Bar.phpnamespaceOtherDir;useSomeDir\FooasSomeDirFoo;// There is no conflict anymore.
Loading history...
8
use LogicException;
9
use Ray\Di\Exception\Unbound;
10
use ReflectionMethod;
11
12
use function call_user_func_array;
13
use function is_callable;
14
15
final class SetterMethod implements AcceptInterface
16
{
17
/** @var string */
18
private $method;
19
20
/** @var Arguments */
21
private $arguments;
22
23
/**
24
* Is optional binding ?
25
*
26
* @var bool
27
*/
28
private $isOptional = false;
29
30
public function __construct(ReflectionMethod $method, Name $name)
31
{
32
$this->method = $method->name;
33
$this->arguments = new Arguments($method, $name);
34
}
35
36
/**
37
* @param object $instance
38
*
39
* @throws Unbound
40
* @throws Exception
41
*/
42
public function __invoke($instance, Container $container): void
koriym /
Ray.Di
Let?s assume that you have a directory layout like this:
. |-- OtherDir | |-- Bar.php | `-- Foo.php `-- SomeDir `-- Foo.phpand let?s assume the following content of
Bar.php:If both files
OtherDir/Foo.phpandSomeDir/Foo.phpare loaded in the same runtime, you will see a PHP error such as the following:PHP Fatal error: Cannot use SomeDir\Foo as Foo because the name is already in use in OtherDir/Foo.phpHowever, as
OtherDir/Foo.phpdoes not necessarily have to be loaded and the error is only triggered if it is loaded beforeOtherDir/Bar.php, this problem might go unnoticed for a while. In order to prevent this error from surfacing, you must import the namespace with a different alias: