Properties (hooks) Other features that can be implemented in php 8.5

[arcanisgk]

Description

Description
Referenced RFC #13455

The following code: https://3v4l.org/5eEWn#v8.3.15

<?php
///on php version < 8.4
class Foo
{
    private $data = null;
    public function issetData(){
        return $this->data !== null;
    }
    public function setData($data){
        $this->data = $data;
    }
}

$foo = new Foo();

var_dump($foo->issetData());

$foo->setData(123);

var_dump($foo->issetData());

output:

bool(false)
bool(true)

---

With the implementation of the Properties Hook we should be able to: https://3v4l.org/QtIpg#v8.4.2

<?php

class Foo
{

    public mixed $data {
        get => $this->data ?? null; //throw new Exception("this property is not set.");
        set => $this->data = $value;
    }
    
    public function issetData(){
        return isset($this->data);
    }
}


$foo = new Foo();

var_dump($foo->issetData());

var_dump($foo->data);

$foo->data = 'Hello World!!!';

var_dump($foo->issetData());

var_dump($foo->data);

output:

bool(false)
NULL
bool(true)
string(14) "Hello World!!!"

I think this is still halfway there, I think I should be able to do this:

https://3v4l.org/Q6Ep9#v8.4.2

<?php

class Foo
{

    public mixed $data {
        get => $this->data ?? null; //throw new Exception("this property is not set.");
        set => $this->data = $value;
        isset => isset($this->data);
    }
}

$foo = new Foo();

//option 1

var_dump(?$foo->data); // This should produce the same output as an "isset" implemente "?" at begining
// Expected output: false

//option 2

var_dump($foo->data?isset); // This should join on "isset" hook, implement ?isset at end
// Expected output: false

//Option 3: Create a shorthand symbol for isset like the two examples above but without the hook

would it be possible?

[iluuu1994]

You can use isset() outside the class as well. https://3v4l.org/CNFFF What's wrong with that? It will return false if your get hook returns null.

[arcanisgk]

"isset" is not OOP... and I don't feel comfortable when we already have something like property hook...

[iluuu1994]

Why? isset specifically works with property hooks. It respects the get hook and acts appropriately. I don't know what you mean by it not being OOP. Why would it have to be?

[arcanisgk]

@iluuu1994 becouse this:

It doesn't work the same...

<?php

class Foo
{

    public mixed $data {
        get => $this->data;
        set => $this->data = $value;
    }
}


$foo = new Foo();


// var_dump(isset($foo->data)); 
// output: Fatal error: Uncaught Error: Typed property Foo::$data must not be accessed before initialization in


class Foo2
{

    public mixed $data;
}


$foo2 = new Foo2();


var_dump(isset($foo2->data));//work well
//output: bool(false)

But don't worry, I already removed the request, so we don't go bald... hook implementation does not respect the usual isset...