Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:111404
Message-ID: <E6C6FE8B-C263-46AB-B851-14DEB4AED52A@joshbruce.dev>
Content-Type: multipart/alternative;
	boundary="Apple-Mail=_E4E83673-5EC7-49A8-A934-7A754BE358D5"
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.1\))
Date: Sun, 9 Aug 2020 14:54:17 -0500
In-Reply-To: <1bc7759a-63b8-4b96-bb69-97b50f851307@www.fastmail.com>
Cc: php internals <internals@lists.php.net>
To: Larry Garfield <larry@garfieldtech.com>
References: <21C5073D-3F39-49DA-8686-E027AE780793@joshbruce.dev>
 <D14A346D-6234-4A85-9266-4125236B3F3E@joshbruce.dev>
 <1bc7759a-63b8-4b96-bb69-97b50f851307@www.fastmail.com>
Subject: Re: [PHP-DEV] [RFC][Discussion] Objects can be declared falsifiable
From: josh@joshbruce.dev (Josh Bruce)

--Apple-Mail=_E4E83673-5EC7-49A8-A934-7A754BE358D5
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

Trying not to drown the list while some RFCs are getting worked out and =
preparing for 8.0.

Quick update:

1. Walking through Nikita=E2=80=99s instructions - writing about it =
here: =
https://joshbruce.dev/essays/software-development/php-falsifiable-objects =
<https://joshbruce.dev/essays/software-development/php-falsifiable-objects=
>

2. I agree some type of working concept should be a thing.

3. Have some other projects taking precedent, any assistance on =
implementation would be greatly appreciated.

Cheers,
Josh

> On Jul 22, 2020, at 7:49 AM, Larry Garfield <larry@garfieldtech.com> =
wrote:
>=20
> On Tue, Jul 21, 2020, at 10:34 AM, Josh Bruce wrote:
>> Learning more everyday. This thread will be the =E2=80=9Cofficial =
thread=E2=80=9D -=20
>> other related threads have been added to the RFC (including one from =
11=20
>> years ago): https://bit.ly/php-0002-rfc <https://bit.ly/php-0002-rfc>
>>=20
>> Created fork - with PR on fork to explore and leave notes without=20
>> hitting the mailing list with every little thing:=20
>> https://github.com/joshbruce/php-src/pull/1=20
>> <https://github.com/joshbruce/php-src/pull/1>
>>=20
>> Will be letting this cool down for the recommended two weeks while I=20=

>> learn the things and PHP 8 is prepared for release.
>>=20
>> Not sure if this should be put up for a vote before or after the=20
>> implementation based on what I=E2=80=99ve read so. Seems the =
recommendation is=20
>> the vote first - unless sample implementation seems like it would be=20=

>> helpful. I think it would; so, will proceed on the implementation=20
>> course pending feedback.
>>=20
>> Thanks again for all the feedback, questions, and concerns!
>>=20
>> Cheers,
>> Josh
>=20
> I'd say it's bad form to call a vote on something without at least a =
partial implementation and a path to finish the implementation.  =
Otherwise, even if it passes it may not happen and that's just all kinds =
of confusing.  The code doesn't have to be perfect, but at least enough =
to demonstrate it can be done and won't cause a 50% performance =
regression.  That also gives voters confidence that if the RFC passes =
the code will actually get completed by the people that proposed it, =
rather than just expecting someone else to magically do it for them.
>=20
> --Larry Garfield
>=20
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: https://www.php.net/unsub.php
>=20


--Apple-Mail=_E4E83673-5EC7-49A8-A934-7A754BE358D5--