Trait conflict resolution in PHP - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ Predict Output

intermediate

Output of trait method conflict resolution with 'insteadof'

What is the output of this PHP code that uses two traits with conflicting method names resolved by 'insteadof'?

PHP

<?php
trait A {
    public function sayHello() {
        return "Hello from A";
    }
}
trait B {
    public function sayHello() {
        return "Hello from B";
    }
}
class Greeting {
    use A, B {
        B::sayHello insteadof A;
    }
}
$greet = new Greeting();
echo $greet->sayHello();

A Hello from A

B Hello from B

C Fatal error: Trait method sayHello has not been applied, because there are collisions

D Hello from A and B

💡 Hint

Look at which trait's method is chosen by the 'insteadof' operator.

The 'insteadof' operator tells PHP to use B's sayHello method instead of A's when both traits have the same method name.

❓ Predict Output

intermediate

Output when aliasing trait methods with 'as'

What will this PHP code output when aliasing a trait method with 'as' to create a new method name?

PHP

<?php
trait X {
    public function greet() {
        return "Hello from X";
    }
}
class Y {
    use X {
        greet as sayHi;
    }
}
$y = new Y();
echo $y->sayHi();

A Hello from X

B Hello from Y

C Fatal error: Call to undefined method Y::sayHi()

D Hello from X and Y

💡 Hint

Aliasing creates a new method name pointing to the original trait method.

The 'as' keyword creates an alias sayHi for the greet method from trait X, so calling sayHi() works and returns the original method's string.

🔧 Debug

advanced

Identify the error in trait conflict resolution

This PHP code tries to resolve a method conflict between two traits but causes an error. What is the error message?

PHP

<?php
trait T1 {
    public function action() {
        return "Action from T1";
    }
}
trait T2 {
    public function action() {
        return "Action from T2";
    }
}
class C {
    use T1, T2 {
        action;
    }
}
$c = new C();
echo $c->action();

A Fatal error: Trait method action has not been applied, because there are collisions

B Action from T1

C Action from T2

D Parse error: syntax error, unexpected ';' in class C

💡 Hint

Check the syntax of the conflict resolution block inside the use statement.

The line 'action;' inside the use block is invalid syntax. You must specify how to resolve the conflict using 'insteadof' or 'as'.

❓ Predict Output

advanced

Output when using both 'insteadof' and 'as' in trait conflict resolution

What is the output of this PHP code that uses 'insteadof' to resolve conflict and 'as' to alias a method?

PHP

<?php
trait Alpha {
    public function speak() {
        return "Alpha speaking";
    }
}
trait Beta {
    public function speak() {
        return "Beta speaking";
    }
}
class Speaker {
    use Alpha, Beta {
        Alpha::speak insteadof Beta;
        Beta::speak as speakBeta;
    }
}
$s = new Speaker();
echo $s->speak() . ' and ' . $s->speakBeta();

A Alpha speaking and Alpha speaking

B Beta speaking and Alpha speaking

C Alpha speaking and Beta speaking

D Fatal error: Call to undefined method Speaker::speakBeta()

💡 Hint

The 'insteadof' chooses which speak() method is default, 'as' creates an alias for the other.

The class uses Alpha's speak() method by default, but Beta's speak() is still accessible via the alias speakBeta().

🧠 Conceptual

expert

Understanding trait conflict resolution priority

Given two traits with the same method name used in a class, which statement about PHP trait conflict resolution is true?

A PHP throws a fatal error if two traits have the same method name and no conflict resolution is provided.

B If no conflict resolution is specified, PHP uses the method from the trait listed first in the use statement.

C PHP automatically merges the two methods into one combined method.

D The class's own method always overrides trait methods, even if not declared explicitly.

💡 Hint

Think about what happens when PHP encounters two methods with the same name from different traits without instructions.

PHP requires explicit conflict resolution when two traits have methods with the same name; otherwise, it throws a fatal error.