Aliased methods imported from a trait misidentify themselves by their original name during call interception

[antecedent]

Let's say we have a trait with a single method:

trait FooSayingTrait
{
    static function speak()
    {
        echo "foo";
    }
}

This trait is used by a class, importing the trait's method under a different name. The original name of the imported method is taken by a new method:

class Babbler
{
    use FooSayingTrait {
        speak as sayFoo;
    }

    static function speak()
    {
        echo "bar";
    }
}

Now attempting to redefine the sayFoo method, imported from FooSayingTrait, will fail, albeit without producing any errors:

Patchwork\replace("Babbler::sayFoo", function() {
    echo "spam";
});

Babbler::sayFoo(); # prints "foo", not "spam" as one would expect

This happens because everytime Babbler::sayFoo is called, it identifies itself with Patchwork by its original name, that is, Babbler::speak. Since there aren't yet any patches for Babbler::speak, the original implementation of this method runs. (For the actual call interception code that Patchwork makes run on every call to a user-defined function, see CALL_INTERCEPTION_CODE.)

This is supported by the fact that trying to redefine Babbler::speak will redefine Babbler::sayFoo as well:

Patchwork\replace("Babbler::speak", function() {
    echo "eggs";
});

Babbler::speak(); # prints "eggs"
Babbler::sayFoo(); # prints "eggs", not "foo" or "spam" as it should

[antecedent]

Sadly, I'm unlikely to fix this by myself anytime soon due to serious health issues that I've also mentioned here.

[antecedent]

Sadly, I'm unlikely to fix this by myself anytime soon due to serious health issues that I've also mentioned here.

[antecedent]

Nevermind — this is now fixed in version 1.2.0.

[antecedent]

Nevermind — this is now fixed in version 1.2.0.