Re: RFC - Immutable classes
| From: | Fleshgrinder | Date: | Mon, 08 Aug 2016 16:44:00 +0000 |
| Subject: | Re: RFC - Immutable classes | ||
| References: | 1 2 3 4 5 6 7 8 9 10 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-94938@lists.php.net to get a copy of this message | ||
On 8/8/2016 5:00 PM, Silvio Marijić wrote:
> It's great that you are up of this.
> I think it will be great to see this one in action.
>
> I agree that we should separate them into separate RFC-s.
>
> 2016-08-08 15:51 GMT+02:00 Michał Brzuchalski <michal@brzuchalski.com>:
>
>> It is great to hear somone is interested so why not. My lately discussion
>> found usefull implementing 3 keywords, such as:
>> 1. *immutable* for the functionality you are currently working on.
>> 2. *sealed* for the above plus type not changeable.
>> 3. *final* for the above plus not being overridable.
>>
>> But all of them should be implemented in different RFC's starting from
>> Immutable because it's base point to toher two keywords.
>> Whole idea needs refreshing discussion to clarify idea so it can success.
>>
I would like to offer my support. I might not be as familiar as you guys
with the C source but if you need anything (e.g. documentation, RFC
writing, testing, ...) let me know.
--
Richard "Fleshgrinder" Fussenegger
Attachment: [application/pgp-signature] OpenPGP digital signature signature.asc
Attachment: [application/pgp-signature] OpenPGP digital signature signature.asc