Re: [PHP-DEV] Re: Release Managers for PHP 8.1

2021-03-23 Thread Gunnard Engebreth
On 3/23/21 10:48 AM, Sara Golemon wrote: On Tue, Mar 23, 2021 at 10:31 AM Harm Smits wrote: That reminded me to create the 8.1 TODO: https://wiki.php.net/todo/php81 Amazing! Just one remark, my name is spelled wrong ;) Its "Smits", not "Smitts". Whoopsie. Fixed. Feel free to change anythi

Re: [PHP-DEV] [RFC] Deprecations for PHP 8.1

2021-03-23 Thread Kalle Sommer Nielsen
Hi Den man. 22. mar. 2021 kl. 11.25 skrev Nikita Popov : > > Hi internals, > > It's time for another deprecation RFC: > https://wiki.php.net/rfc/deprecations_php_8_1 I'd like to suggest adding `nl_langinfo()` to the list of deprecations, it is a non-cross platform oddity that make less sense with

Re: [PHP-DEV] Re: Release Managers for PHP 8.1

2021-03-23 Thread Sara Golemon
On Tue, Mar 23, 2021 at 2:44 PM Patrick ALLAERT wrote: > You mean a veteran RM, not a veteran participant of this ML, right? > Correct. Though I should also note that for the 7.2 release, neither Remi nor I had experience. So there is precedent for two newbies. It helped that Remi and I were b

Re: [PHP-DEV] Re: Release Managers for PHP 8.1

2021-03-23 Thread Harm Smits
> The idea of having a couple of rookie Release Managers to one veteran > would be nice. Then when the role for the next Release Manager comes up, > letting one (or both) of the rookie(s) step up as the veteran and giving > the other rookie the option to pair again also with a "fresh rookie". That

Re: [PHP-DEV] [RFC] Pure intersection types

2021-03-23 Thread Matthew Brown
On Tue, 23 Mar 2021 at 05:32, G. P. B. wrote: > I'm calling this proposal pure intersection types as there would be no > possibility of mixing intersection and union types, I'm leaving this as a > future scope. > Does this miss an opportunity, though? It's useful to be able to write A&B|null.

Re: [PHP-DEV] Re: Release Managers for PHP 8.1

2021-03-23 Thread Patrick ALLAERT
Hi, Le lun. 22 mars 2021 à 21:24, Sara Golemon a écrit : > A gentle reminder to submit yourselves for the PHP 8.1 Release Manager > job. It really takes nothing more than a little bit of time. > > We've got two "newbie" volunteers already, but we should ideally have a > veteral available. So I

Re: [PHP-DEV] Re: Release Managers for PHP 8.1

2021-03-23 Thread Eric Van Johnson
I am interested in helping with the Release Manager role for the next release of PHP. I like a lot of the ideas being discussed here around the role, such as; - The idea of having a couple of rookie Release Managers to one veteran would be nice. Then when the role for the next Release Manag

Re: [PHP-DEV] [RFC] Phasing out Serializable

2021-03-23 Thread Björn Larsson
Den 2021-03-23 kl. 18:19, skrev Nikita Popov: On Tue, Mar 23, 2021 at 5:01 PM Nicolas Grekas mailto:nicolas.grekas%2b...@gmail.com>> wrote: Hello Nikita, Picking up a loose thread: https://wiki.php.net/rfc/custom_object_serialization

Re: [PHP-DEV] [RFC] Phasing out Serializable

2021-03-23 Thread Nikita Popov
On Tue, Mar 23, 2021 at 5:01 PM Nicolas Grekas wrote: > Hello Nikita, > > > Picking up a loose thread: >> https://wiki.php.net/rfc/custom_object_serialization introduced a >> replacement for Serializable in PHP 7.4, so it's time to think about >> deprecating and removing the old mechanism: >> >>

Re: [PHP-DEV] Re: Release Managers for PHP 8.1

2021-03-23 Thread Harm Smits
@Sara Hereby, a proper introduction. I have been actively developing in PHP, along with some other programming languages, for the past 7 years. I would love to put my experience to good use and help out with the 8.1 release of PHP. I have been using CI / CD for the better part of 5 years and belie

Re: [PHP-DEV] [RFC] Phasing out Serializable

2021-03-23 Thread Nicolas Grekas
Hello Nikita, Picking up a loose thread: > https://wiki.php.net/rfc/custom_object_serialization introduced a > replacement for Serializable in PHP 7.4, so it's time to think about > deprecating and removing the old mechanism: > > https://wiki.php.net/rfc/phase_out_serializable > > This RFC follow

Re: [PHP-DEV] Re: Release Managers for PHP 8.1

2021-03-23 Thread Sara Golemon
On Tue, Mar 23, 2021 at 10:31 AM Harm Smits wrote: > > That reminded me to create the 8.1 TODO: https://wiki.php.net/todo/php81 > > Amazing! Just one remark, my name is spelled wrong ;) Its "Smits", not > "Smitts". > Whoopsie. Fixed. Feel free to change anything on the line referencing you. L

Re: [PHP-DEV] Re: Release Managers for PHP 8.1

2021-03-23 Thread Harm Smits
> That reminded me to create the 8.1 TODO: https://wiki.php.net/todo/php81 Amazing! Just one remark, my name is spelled wrong ;) Its "Smits", not "Smitts".

Re: [PHP-DEV] [VOTE] Fibers

2021-03-23 Thread Niklas Keller
Hey all, I've closed the vote and I'm happy to report that the RFC has been accepted with 78.125% in favor (50:14). I've moved the RFC to the landing state on https://wiki.php.net/rfc#pending_implementationlanding Thank you all for voting and taking part in the discussion! I'll follow-up once t

[PHP-DEV] [RFC] Object-scope RNG again

2021-03-23 Thread Go Kudo
Hi internals. The Fiber vote appears to have passed. Congratulations! Now, while Fiber is a very nice feature, it has increased the severity of MT's global state problems. I have prepared an example using amphp. It is difficult to predict the results of the following run, and there appears to be

Re: [PHP-DEV] [RFC] Pure intersection types

2021-03-23 Thread G. P. B.
On Tue, 23 Mar 2021 at 13:14, Larry Garfield wrote: > On Tue, Mar 23, 2021, at 4:32 AM, G. P. B. wrote: > > Greetings internals, > > > > I'm presenting a new RFC to add support for pure intersection types to > PHP. > > > > An intersection type A&B means that the value must be of type A and of > t

Re: [PHP-DEV] [RFC] Pure intersection types

2021-03-23 Thread someniatko
> Should we be planning ahead for some future where union and intersection > types can be mixed and design the reflection API accordingly? I worry that > if we have a ReflectionIntersectionType, and a ReflectionUnionType, that > ReflectionIntersectionAndUnionType is just going to make both impl

Re: [PHP-DEV] Re: Release Managers for PHP 8.1

2021-03-23 Thread Sara Golemon
On Tue, Mar 23, 2021 at 8:32 AM Sara Golemon wrote: > On Tue, Mar 23, 2021 at 6:47 AM Harm Smits wrote: > >> > It's not first-come-first-served, we're calling for volunteers and will >> have a vote in mid-April (see initial post from me). Though attention to >> detail in written instructions is

Re: [PHP-DEV] Re: Release Managers for PHP 8.1

2021-03-23 Thread Sara Golemon
On Tue, Mar 23, 2021 at 6:47 AM Harm Smits wrote: > > It's not first-come-first-served, we're calling for volunteers and will > have a vote in mid-April (see initial post from me). Though attention to > detail in written instructions is a plus *wink* ;) > > Oh amazing. Any need for an introducti

Re: [PHP-DEV] [RFC] Pure intersection types

2021-03-23 Thread Larry Garfield
On Tue, Mar 23, 2021, at 4:32 AM, G. P. B. wrote: > Greetings internals, > > I'm presenting a new RFC to add support for pure intersection types to PHP. > > An intersection type A&B means that the value must be of type A and of type > B at the same time. > > I'm calling this proposal pure inters

Re: [PHP-DEV] Re: Release Managers for PHP 8.1

2021-03-23 Thread Harm Smits
> It's not first-come-first-served, we're calling for volunteers and will have a vote in mid-April (see initial post from me). Though attention to detail in written instructions is a plus *wink* ;) Oh amazing. Any need for an introduction or something along the likes of that (for the vote)?

Re: [PHP-DEV] [RFC] Pure intersection types

2021-03-23 Thread Marco Pivetta
Hey George, On Tue, Mar 23, 2021 at 10:32 AM G. P. B. wrote: > Greetings internals, > > I'm presenting a new RFC to add support for pure intersection types to PHP. > > An intersection type A&B means that the value must be of type A and of type > B at the same time. >

[PHP-DEV] [RFC] Pure intersection types

2021-03-23 Thread G. P. B.
Greetings internals, I'm presenting a new RFC to add support for pure intersection types to PHP. An intersection type A&B means that the value must be of type A and of type B at the same time. I'm calling this proposal pure intersection types as there would be no possibility of mixing intersecti