On Sun, 25 Apr 2021 22:56:26 +0100 Chase Peeler
wrote
> On Sun, Apr 25, 2021 at 11:36 AM Mike Schinkel wrote:
>
> >
> >
> > > On Apr 24, 2021, at 7:39 PM, David Gebler wrote:
> > >
> > > I don't love this idea, I'm not very fond of the final keyword, either;
> >
>
ilto:internals@lists.php.net> wrote:
> >
> > On Sat, Apr 24, 2021 at 8:04 AM Benjamin Eberlei
> > <mailto:kont...@beberlei.de> wrote:
> >>
> >>> On Sat, Apr 24, 2021 at 2:56 PM Pierre <mailto:pierre-...@processus.org>
> >
On Sun, 25 Apr 2021 08:39:37 +0100 Olle Härstedt
wrote
> > In practice, I think all of the use cases for sealed classes are
> > ADT-esque.
> > As I noted before, combining sealed classes with Nikita's
> > new-in-expressions
> > RFC would allow for this (also using my
e any
hacks.
On Sat, 24 Apr 2021 16:52:20 +0100 Olle Härstedt
wrote
2021-04-24 12:56 GMT, Pierre <mailto:pierre-...@processus.org>:
> Le 24/04/2021 à 12:55, Saif Eddin Gmati a écrit :
>> Hello Internals,
>>
>> I'm sending this email
gt; On Sat, Apr 24, 2021 at 2:56 PM Pierre <mailto:pierre-...@processus.org>
>>> wrote:
>>>
>>> Le 24/04/2021 à 12:55, Saif Eddin Gmati a écrit :
>>>> Hello Internals,
>>>>
>>>> I'm sending this email to open discussion about sealed cla
a final interface.
‐‐‐ Original Message ‐‐‐
On Saturday, April 24, 2021 11:55 AM, Saif Eddin Gmati
wrote:
> Hello Internals,
>
> I'm sending this email to open discussion about sealed classes, interfaces,
> and traits feature for PHP 8.1.
>
> I have create a Dra
Hello Internals,
I'm sending this email to open discussion about sealed classes, interfaces, and
traits feature for PHP 8.1.
I have create a Draft RFC here: https://wiki.php.net/rfc/sealed_classes
A major concern for few people have been the syntax, in which it introduces 2
new keywords into
Hello Internals,
I'm sending this email to open discussion about sealed classes, interfaces, and
traits feature for PHP 8.1.
I have create a Draft RFC here: https://wiki.php.net/rfc/sealed_classes
A major concern for few people have been the syntax, in which it
introduces 2 new keywords into
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hello Internals,
I'm requesting karma to open an RFC for sealed classes feature.
wiki username: azjezz
-BEGIN PGP SIGNATURE-
Version: ProtonMail
wsFzBAEBCAAGBQJggxwSACEJELAOCkaz8cFXFiEEOazMpP0wDQTIQG6zsA4K
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hello,
I would like to introduce myself to those of you who might not know me.
My name is Saif ( also known as "azjezz" ), I'm 21 years old, i have been
working with PHP for approximately 8 years.
I'm currently employed as a senior developer at
Hello Hamza,
I think this is something that has been discussed here before.
function types already exist in HackLang:
https://docs.hhvm.com/hack/functions/introduction#function-types,
And, if we would follow the same syntax `(function(T, T): T)` or `(callable(T,
T): T)`, PHP needs to first
Personally, I am against the syntax used in the PR for composite
types( even tho i don't have voting powers ).
I would prefer a syntax similar to Hack, where you have to use parentheses to
make things more explicit.
considering the following Hack code:
interface A {}
interface B {}
Hello Sara,
I would like to volunteer as a newbie RM.
I don't have much experience with php-src it self, but i have been
involved in PHP community as a whole for a while, and would like to try and
help out.
Regards,
Saif.
https://void.tn
‐‐‐ Original Message ‐‐‐
On Monday, March
Hey Matthew,
I have look at the implementation a few days ago, and was patiently waiting for
the RFC.
a huge +1 from me ( even tho i can't vote ), `noreturn` type would be a great
addition to PHP type system.
Regards,
Saif.
‐‐‐ Original Message ‐‐‐
On Wednesday, March 10, 2021
Hello Aaron,
First, I want to say that I love this proposal and would love to see it land in
the next PHP release, but I have one question regarding this:
> Promises result in the “What color is your function” problem as described in
> the introduction of the RFC. Returning promises from
Really excited to see the discussion about this feature being brought up again,
thanks for working on this :)
One thing I would suggest is to add a base interface `Attribute` and multiple
sub-interfaces such as `ClassAttribute`, `MethodAttribute`, and
`PropertyAttribute` just like hack lang (
Really excited to see the discussion about this feature being brought up again,
thanks for working on this :)
One thing I would suggest is to add a base interface `Attribute` and multiple
sub-interfaces such as `ClassAttribute`, `MethodAttribute`, and
`PropertyAttribute` just like hack lang (
17 matches
Mail list logo
