no please no "mixed" keyword
my idea to this is having something like this:
class Foo { public function test (int $a) : int { return $a; } }
class Bar extends Foo { override public function test (string $a) :
string { return $a; } }
class FooBar extends Foo { override public function test ($a) {
Results for project PHP master, build date 2016-11-29 06:26:31+02:00
commit: d1f9d37
previous commit:f0ba9ab
revision date: 2016-11-29 06:45:01+09:00
environment:Haswell-EP
cpu:Intel(R) Xeon(R) CPU E5-2699 v3 @ 2.30GHz 2x18 cores,
stepping 2, LLC 45 MB
But this leads to code that can't pass static inspections?
interface Joiner {
public function join(array $array): string;
}
class WideJoiner implements Joiner {
public function join($iterable): string {
$array = is_array($iterable) ? $array :
iterable_to_array($iterable);
>
> But this leads to code that can't pass static inspections?
>
No.
> interface Joiner {
> public function join(array $array): string;
> }
>
> class WideJoiner implements Joiner {
> public function join($iterable): string {
> $array = is_array($iterable) ? $array :
> iterable_to
On Mon, Nov 21, 2016 at 10:39 AM, Niklas Keller wrote:
> Morning Internals,
>
> I'd like to announce a RFC to allow omitting the type declarations for
> parameters in subclasses:
> https://wiki.php.net/rfc/parameter-no-type-variance
>
> PHP doesn't currently allow variance for parameters as check
Hi Adam,
On 29/11/2016 00:16, Adam Baratz wrote:
> I'd be happy to make the feature more specific. The "Parsed" line would
> only show with emulated prepares enabled, after execute() has been called.
> I'd prefer using "Parsed" because the language would be more specific. It
> would also correspon
Hi Markus,
On Sat, Nov 19, 2016 at 1:15 PM, Yasuo Ohgaki wrote:
>> Btw, what is the proper way to signal a problem during
>> serialization/unserialization? I couldn't figure it out from the RFC nor
>> the PR and there doesn't seem to be a test case for it.
>> Return null/false? Throw an exception