Req #70472 [Opn->Sus]: prevent trait to be used when conflicts can't be resolved

From: Date: Sat, 05 Aug 2017 04:47:09 +0000
Subject: Req #70472 [Opn->Sus]: prevent trait to be used when conflicts can't be resolved
References: 1  Groups: php.bugs 
Request: Send a blank email to php-bugs+get-210509@lists.php.net to get a copy of this message
Edit report at https://bugs.php.net/bug.php?id=70472&edit=1

 ID:                 70472
 Updated by:         stas@php.net
 Reported by:        youwishspambot at example dot orgy
 Summary:            prevent trait to be used when conflicts can't be
                     resolved
-Status:             Open
+Status:             Suspended
 Type:               Feature/Change Request
 Package:            Scripting Engine problem
 Operating System:   any
 PHP Version:        7.0.0RC2
 Block user comment: N
 Private report:     N

 New Comment:

Thank you for your interest in PHP and for submitting a feature request. Please be aware that due to
the magnitude of change this request requires, it would be necessary to discuss it on PHP Internals
list (internals@lists.php.net) as an RFC. Please read the guide about creating RFCs here:
https://wiki.php.net/rfc/howto
If you haven't had experience with writing RFCs before, it is advised to seek guidance on the
Internals list (http://php.net/mailing-lists.php) and/or solicit help from one of the experienced
developers. 

Please to not consider this comment as a negative view on the merits of your proposal - every
proposal which requires changes of certain magnitude, even the very successful and widely supported
ones, must be done through the RFC process. This helps make the process predictable, transparent and
accessible to all developers.


Previous Comments:
------------------------------------------------------------------------
[2015-09-10 19:34:32] youwishspambot at example dot orgy

Description:
------------
Example 1:

<?php

class A{}
class B{}

trait X{
    abstract function test(B $b);
    function doSomething(){
        // can only be B. nothing should be allowed to change the signature of test(B)
        $this->test(new B);
    }
}

interface Contract{
    function test(A $a);
}

class Implementation implements Contract{
    use X; // incompatible, but compiles
    function test(A $a){}
}

-------------------------------------------------------

Example 2:

<?php

class A{}
class B{}

trait X{
    function tryA(A $a){
        $this->test($a);
    }
    function test(A $a){} // can't solve signatures incompatibility...
}

trait Y{
    function tryB(B $b){
        $this->test($b);
    }
    function test(B $b){} // ...when arguments are different
}


class Example{
    use X, Y{
        X::test insteadof Y; // this doesn't actually solve anything
    }
}

class A{}
class B{}

$x = new Example;
$x->tryA(new A);
$x->tryB(new B);

(insteadof can only work if resolution happens between two identical signatures)



------------------------------------------------------------------------



--
Edit this bug report at https://bugs.php.net/bug.php?id=70472&edit=1


Thread (1 message)

  • stas@php.net
  • Unknown Message
    • stas@php.net
« previous php.bugs (#210509) next »