Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:98485
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.161.173 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <CAEDdnaXrRnYQ24Dh7RdYmVdiYbBcXjnxo4_B0cNFe=FGewEbvQ@mail.gmail.com>
References: <CAEDdnaXrRnYQ24Dh7RdYmVdiYbBcXjnxo4_B0cNFe=FGewEbvQ@mail.gmail.com>
Date: Sat, 11 Mar 2017 21:24:13 +0500
Message-ID: <CAEDdnaV+pEyCn1nsMn8WAdNTX8+buynhCfP6e0h0JTcUhygBzQ@mail.gmail.com>
To: PHP Internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=94eb2c0612c0ae51d2054a76e849
Subject: Re: [PHP-DEV] Type variants
From: michael.vostrikov@gmail.com (Michael Vostrikov)

--94eb2c0612c0ae51d2054a76e849
Content-Type: text/plain; charset=UTF-8

> 'Order does not match OrderForCheckout. Reason: ...'.

Sorry, this is text for second example) I missed this moment. But I think
the idea is clear.


For manual call of __match() type casting can be used:
$orderForCheckout = (OrderForCheckout)$order;


Also this feature can be used for checking enum values or intervals.

class Value
{
    public $value;

    public function __construct($value)
    {
        $this->value = $value;
    }
}

class State variant of Value
{
    const ACTIVE = 1;
    const INACTIVE = 2;

    public function __match()
    {
        return in_array($this->value, [self::ACTIVE, self::INACTIVE]);
    }
}

function setState(State $s)
{
    ...
}

setState(new State(3));

In constructions like "new State($value)" __match() can be called after
__construct().


If to add a possibility to use data types, class Value will not be needed:

class State variant of integer
{
    ...
    public function __match()
    {
        return in_array($this, [self::ACTIVE, self::INACTIVE]);
    }
}

setState(3);

--94eb2c0612c0ae51d2054a76e849--