Issue with the order of used inherited traits since 8.3.8/8.2.20

[lernhart]

Description

The following code:
https://3v4l.org/lFFsD

Resulted in this output:

Fatal error: Uncaught Error: Call to protected method ParentClass::doSomething() from scope ChildClass in /in/lFFsD:25
Stack trace:
#0 /in/lFFsD(29): ChildClass->__construct()
#1 {main}
  thrown in /in/lFFsD on line 25

Process exited with code 255.

But I expected this output instead:

FOO (result of method of parent trait)

The order of the used traits does matter since 8.3.8 and 8.2.20.
As seen in the 3v4l example, the trait TraitA, which implements the method is used after the TraitB, which declares the abstract method.

The order of the traits does not matter, if the child class directly uses the traits.

This commit may relate to the issue ?

PHP Version

8.3.8

Operating System

No response

[mvorisek]

Probably duplicate of already fixed #14480.

Maybe issue a hotfix patch releases on top of the latest ones?

[lernhart]

Didn't catch that ticket, thank you 👍

[ricovandevin]

I have a similar issue with a situation in which a method in a parent class calls a protected method defined in trait that is used by the child class.

<?php

trait someTrait {

  protected function returnSomething() {
    return 'Something';
  }

}

<?php

abstract class parentClass {

  public method doSomething() {
    return $this->returnSomething();
  }

}

<?php

class childClass extends parentClass {

  use someTrait;

}

$class = new childClass();
$class->doSomething();

leads to an error

Error: Call to protected method childClass::returnSomething() from scope parentClass