Class resolution fails to check namespace first

[markkimsal]

Verified on latest main

• I have confirmed this bug still occurs when built from the latest main branch.

PHPantom version / commit

9092234

Installation method

Built from source

Operating system

Linux x86_64

Editor

VS Code

Bug description

Class resolution checks global namespace before current namespace for sibling classes.

According to:
https://www.php.net/manual/en/language.namespaces.fallback.php

Inside a namespace, an unqualified Name resolves to the current namespace, un-namespaced classes must be accessed with \ specifically

Steps to reproduce

mkdir -p tmp/{src,legacy}

cat <<'EOD' >> tmp/src/A.php
<?php

namespace Src;

class A {
        public static function y(): void {
                B::x();
        }
}
EOD

cat <<'EOD' >> tmp/src/B.php
<?

namespace Src;


class B {
        public static function x(): void {
                echo "x\n";
        }
}
EOD

cat <<'EOD' >> tmp/legacy/B.php 
<?php

class B {

}
EOD

### Error output or panic trace

```text
./target/release/phpantom_lsp analyze tmp/
  3/3 [▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓] 100%
 ------ -----------------------------------
  Line   tmp/src/A.php
 ------ -----------------------------------
     7   Method 'x' not found on class 'B'
         🪪  unknown_member
 ------ -----------------------------------


                        
  [ERROR] Found 1 error

.phpantom.toml

Additional context

workaround is to add explicit use Src/B;

[Metrol]

Seems that I've got a "me too" on this one. In my case, I've got a namespace that roughly looks like: Site\View with a class name Event.

The part of the code that instantiates the new View\Event() class, phpantom thinks I'm trying to access a PHP Event object. Just to double check, I reverted back to intelephense which was able to correctly resolve what was meant.

I've been quite happily using phpantom for a little over a week, and this is the first glitch I've personally run into. If there's any additional information I can provide to help out please let me know.

[AJenbo]

I'm hoping to get a new release ready in about a week and will include a fix for this then. I have a few other bugs to address and need to evaluate how to handle workspace diagnostics before it's ready