Le 07/12/2020 à 02:00, Paul Crovella a écrit :
On Sun, Dec 6, 2020 at 7:12 AM Rowan Tommins <rowan.coll...@gmail.com> wrote: Longer term plans are irrelevant except to avoid inadvertently shutting the door on something. This RFC is up for discussion, and will be up for voting, in isolation. It has to be able to stand on its own.
I strongly disagree with you. Something as important as new type-related paradigm must be considered along its full roadmap. This enum RFC tries to prepare the future, and if it wasn't, tagged unions and ADT wouldn't be possible at all. Since they are all sensible changes, having a roadmap is what makes all consistent, it must be considered and discussed along its global roadmap.
You probably should consider that enum cases using singleton classes only as being an implementation detail, not a high-level design choice, if you start to mix up real classes with those enum cases, future low level engine or compiler improvement, for performance or consistency, will not be possible anymore because people will be stuck in using them as classes, which they are not conceptually.
Any failure in considering the future will result in a tight awkward situation were improvements will not be possible anymore.
Regards, Pierre -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: https://www.php.net/unsub.php
