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. 2016-08-08 15:23 GMT+02:00 Silvio Marijić <marijic.sil...@gmail.com>: > @Michal Would you consider cooperating on implementing immutable and > sealed modifiers? > > 2016-08-08 15:20 GMT+02:00 Michał Brzuchalski <mic...@brzuchalski.com>: > >> @Silvio I've tried to implement final https://github.com/php/p >> hp-src/compare/master...brzuchal:final-properties but haven't found time >> to implement immutable and sealed, AFAIK I had problems with OPcache >> enabled, you need to remember to run every test after compile with opcache >> enabled in CLI. >> >> 2016-08-08 15:00 GMT+02:00 Silvio Marijić <marijic.sil...@gmail.com>: >> >>> @Michal, well no I did read it. I see that there is not much going on >>> there since last year. Did you tried to implement it ? >>> >>> 2016-08-08 14:49 GMT+02:00 Michał Brzuchalski <mic...@brzuchalski.com>: >>> >>>> >>>> 2016-08-08 14:47 GMT+02:00 S.A.N <ua.san.a...@gmail.com>: >>>> >>>>> May be better to do as immutable arrays? >>>>> >>>>> const = new Email; >>>>> >>>>> it will be a super global immutable instance of Email. >>>>> >>>> >>>> I think you've missunderstood concept of immutable classes. >>>> >>>> >>>> -- >>>> pozdrawiam >>>> -- >>>> Michał Brzuchalski >>>> >>> >>> >>> >>> -- >>> Silvio Marijić >>> Software Engineer >>> 2e Systems >>> >> >> >> >> -- >> pozdrawiam >> -- >> Michał Brzuchalski >> > > > > -- > Silvio Marijić > Software Engineer > 2e Systems > -- pozdrawiam -- Michał Brzuchalski
