Do not require trait name in trait method alias

[mvorisek]

Description

repro: https://3v4l.org/vE0YH

Currently

    use A {
        A::x as private ax;
    }

is needed to import trait method under different name when such method is defined in more than 1 trait.

There is no ambiguity, I would expect php to understand the:

    use A {
        x as private ax;
    }

as x method from A trait.

[nielsdos]

By reading this issue I deduced the following is possible: https://3v4l.org/sZRVt which is very wtf.
It also makes clear that fixing this behaviour can cause BC break.

[mvorisek]

Currently

    use A {
        x as private ax;
    }
    use B {
        x as private ax;
    }

seems to be processed like:

1. import all use traits
2. resolve the method aliasing against all imported traits in step 1

I assume this based on the exception message:

An alias was defined for method x(), which exists in both A and B. Use A::x or B::x to resolve
the ambiguity

and also based on your repro.

This feature request is to resolve the imports against the last imported use if there was only one trait in that use (ie. not use A, B {...).

This "scoped logic" should no imply any BC break as there is no ambiguity (except no exception/fatal error).

[github-actions]

There has not been any recent activity in this feature request. It will automatically be closed in 14 days if no further action is taken. Please see https://github.com/probot/stale#is-closing-stale-issues-really-a-good-idea to understand why we auto-close stale feature requests.

[mvorisek]

I would be grateful if this can be implemented but I am not C coder.

[github-actions]

There has not been any recent activity in this feature request. It will automatically be closed in 14 days if no further action is taken. Please see https://github.com/probot/stale#is-closing-stale-issues-really-a-good-idea to understand why we auto-close stale feature requests.

[mvorisek]

This is possible, thus not stale.