Re: [PHP-DEV] PHP True Async

> I'm actually curious why you chose libuv? I relied on the usual set of selection criteria: relevance, support, and documentation. Hope there won’t be any serious issues with this component. But if there are, we can implement a Plan B: copy the necessary Win32 code from libUV, adapt it for PHP, a

Re: [PHP-DEV] PHP True Async

On Fri, Feb 14, 2025, at 16:18, Edmond Dantes wrote: > > Yeah we are actually planning better API for this supporting epoll and > > kqueu which is long over due. There are other use cases for this so > > hopefully it will get prioritised soon. > Oh, it would be absolutely great if PHP used a

Re: [PHP-DEV] PHP True Async

> Yeah we are actually planning better API for this supporting epoll and kqueu which is long over due. There are other use cases for this so hopefully it will get prioritised soon. Oh, it would be absolutely great if PHP used a better abstraction for I/O waiting! > You could still achieve this

Re: [PHP-DEV] PHP True Async

On Fri, Feb 14, 2025, at 15:16, Edmond Dantes wrote: > Hello, *Jakub.* > (It seems that simply clicking "Reply" does not work for the conference) > ** > *> *I understand that's not ready for review yet but quickly > You could say that the code is in a state of "architectural stability," so > it

Re: [PHP-DEV] PHP True Async

Hi, On Fri, Feb 14, 2025 at 3:21 PM Edmond Dantes wrote: > Hello, *Jakub.* > (It seems that simply clicking "Reply" does not work for the conference) > > *> *I understand that's not ready for review yet but quickly > You could say that the code is in a state of "architectural stability," > so

Re: [PHP-DEV] PHP True Async

Hello, *Jakub.* (It seems that simply clicking "Reply" does not work for the conference) *> *I understand that's not ready for review yet but quickly You could say that the code is in a state of "architectural stability," so it can be reviewed and criticized. (Unfortunately, only the Windows bui

Re: [PHP-DEV] PHP True Async

On 14.02.2025 at 15:03, Edmond Dantes wrote: >> Have you already registered a new Wiki user? If so, what's your > username? > Yes, I registered today. My login is: edmond. RFC karma granted. Best of luck! Christoph

Re: [PHP-DEV] Re: RFC: Marking return values as important (#[\NoDiscard])

On Fri, Feb 14, 2025 at 1:10 PM Aleksander Machniak wrote: > On 14.02.2025 12:57, Derick Rethans wrote: > > None of the current attributes (ReturnTypeWillChange, > > AllowDynamicProperties, SensitiveParameter, Override, and Deprecated) > > change the behaviour of how a program runs. They only add

Re: [PHP-DEV] PHP True Async

On 14.02.2025 at 12:22, Edmond Dantes wrote: > I would like to request permission to create an RFC dedicated to the > asynchronous module for PHP. Have you already registered a new Wiki user? If so, what's your username? Otherwise head over to . Christoph

Re: [PHP-DEV] PHP True Async

> > >> A brief overview of what this RFC will cover: >> >>1. *True* asynchronous support for PHP core functions without >>additional "tricks." >>2. *Scheduler* and *Reactor* components, providing a C-API for PHP >>extensions to enable non-blocking I/O in plugins or core code. >>

Re: [PHP-DEV] PHP True Async

Hi On Fri, Feb 14, 2025 at 12:24 PM Edmond Dantes wrote: > Good day, everyone. > > I would like to request permission to create an RFC dedicated to the > asynchronous module for PHP. > Someone will surely grant you karma soon. RFC makes sense. > Although the source code development is still in

Re: [PHP-DEV] Re: RFC: Marking return values as important (#[\NoDiscard])

On 14.02.2025 12:57, Derick Rethans wrote: None of the current attributes (ReturnTypeWillChange, AllowDynamicProperties, SensitiveParameter, Override, and Deprecated) change the behaviour of how a program runs. They only add warnings. with the exception of AllowDynamicProperties to be an actual '

Re: [PHP-DEV] Re: RFC: Marking return values as important (#[\NoDiscard])

On Thu, 13 Feb 2025, Tim Düsterhus wrote: > Am 2025-02-13 09:16, schrieb Jakob Givoni: > > > Attributes were added as a structured replacement for docblock props > > and I don't like it when they affect how a program actually runs (as > > long as you're not using reflection). > > Excluding the

Re: [PHP-DEV] Re: RFC: Marking return values as important (#[\NoDiscard])

On Thu, 13 Feb 2025, Larry Garfield wrote: > On Thu, Feb 13, 2025, at 8:16 AM, Tim Düsterhus wrote: > > Hi > > > > Am 2025-02-12 22:31, schrieb Larry Garfield: > >> I'm still undecided on the RFC overall, but one thing that is > >> problematic is the phrasing of the messages. Currently, the mess

Re: [PHP-DEV] Re: RFC: Marking return values as important (#[\NoDiscard])

On Wed, 12 Feb 2025, Volker Dusch wrote: > On Wed, Jan 29, 2025 at 4:12 PM Tim Düsterhus wrote: > > > Volker and I would like to start discussion on our RFC to allow "Marking > > return values as important (#[\NoDiscard])". > > > > Please find the following resources for your reference: > > > >

Re: [PHP-DEV] Introduction - Sam Lewis

Hi Sam On Sat, Feb 8, 2025 at 3:31 PM Sam Lewis wrote: > > I'm new to the PHP community and have enjoyed learning the language over the > past year or so. I saw someone in the Laravel community mention how they > wished PHP had built-in functions for converting temperatures between > Fahrenhei

[PHP-DEV] PHP True Async

Good day, everyone. I would like to request permission to create an RFC dedicated to the asynchronous module for PHP. Although the source code development is still in progress, a significant part of it has already been written, and the initial tests are working successfully. Therefore, I could st

Re: [PHP-DEV] Re: RFC: Marking return values as important (#[\NoDiscard])

On Thu, Feb 13, 2025 at 3:17 PM Tim Düsterhus wrote: > Hi > > Am 2025-02-13 09:16, schrieb Jakob Givoni: > > Attributes were added as a structured replacement for docblock props > > and I > > don't like it when they affect how a program actually runs (as long as > > you're not using reflection).