Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:126679
Precedence: bulk
MIME-Version: 1.0
References: <CAMW7n8AJckEDzhGv9BdjNhq8zAdCqb4HsVr56vGi+izw50X6Dg@mail.gmail.com>
 <CAMW7n8CAbKRY9RZsJNSnehKVv8NNGtygocxc+zHBS4h9iRyUGA@mail.gmail.com>
 <1b6a5b3b-be9b-4e46-9cc6-b8b7f57b8494@app.fastmail.com> <CAMW7n8AumA6bYZ+7+c3rAEeYj0=35wgmohRbrJbH=fc=Ra0FJg@mail.gmail.com>
 <e65708a0-5130-4726-b405-e3185562d770@rwec.co.uk>
In-Reply-To: <e65708a0-5130-4726-b405-e3185562d770@rwec.co.uk>
Date: Sun, 9 Mar 2025 20:13:01 +0200
Message-ID: <CAMW7n8CwR3d0CHsABZA_zQh-29EbtoZm8f84CYv5Z4QkBCLC8g@mail.gmail.com>
Subject: Re: [PHP-DEV] Re: PHP True Async RFC
To: "Rowan Tommins [IMSoP]" <imsop.php@rwec.co.uk>
Cc: internals@lists.php.net
Content-Type: multipart/alternative; boundary="000000000000003c44062feccf05"
From: edmond.ht@gmail.com (Edmond Dantes)

--000000000000003c44062feccf05
Content-Type: text/plain; charset="UTF-8"

>
>  I think the same thing applies to scheduling coroutines: we want the
Scheduler to take over the "null fiber",
>

Yes, you have quite accurately described a possible implementation.
When a programmer loads the initial index.php, its code is already running
inside a coroutine.
We can call it the main coroutine or the root coroutine.

When the index.php script reaches its last instruction, the coroutine
finishes, execution is handed over to the Scheduler, and then everything
proceeds as usual.

Accordingly, if the Scheduler has more coroutines in the queue, reaching
the last line of index.php does not mean the script terminates. Instead, it
continues executing the queue until... there is nothing left to execute.

>
> At that point, the relationship to a block syntax perhaps becomes clearer:
>

Thanks to the extensive discussion, I realized that the implementation with
startScheduler raises too many questions, and it's better to sacrifice a
bit of backward compatibility for the sake of language elegance.

After all, Fiber is unlikely to be used by ordinary programmers.

--000000000000003c44062feccf05
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">&gt;<br>&gt;=C2=A0

I think the same thing applies to scheduling coroutines: we want the Schedu=
ler to take over the &quot;null fiber&quot;,<br>&gt;<div><br></div><div><p>=
Yes, you have quite accurately described a possible implementation.<br>
When a programmer loads the initial <code>index.php</code>, its code is alr=
eady running inside a coroutine.<br>
We can call it the main coroutine or the root coroutine.</p>
<p>When the <code>index.php</code> script reaches its last instruction, the=
 coroutine finishes, execution is handed over to the Scheduler, and then ev=
erything proceeds as usual.</p>
<p>Accordingly, if the Scheduler has more coroutines in the queue, reaching=
 the last line of <code>index.php</code> does not mean the script terminate=
s. Instead, it continues executing the queue until... there is nothing left=
 to execute.</p><p>&gt;<br>&gt;=C2=A0<font color=3D"#333333" face=3D"Fira M=
ono, monospace"><span style=3D"font-size:14px;background-color:rgb(242,242,=
242)">At that point, the relationship to a block syntax perhaps becomes cle=
arer:<br></span></font>&gt;</p><p>Thanks to the extensive discussion, I rea=
lized that the implementation with <code>startScheduler</code> raises too m=
any questions, and it&#39;s better to sacrifice a bit of backward compatibi=
lity for the sake of language elegance.</p><p>
</p><p>After all, <code>Fiber</code> is unlikely to be used by ordinary pro=
grammers.</p></div></div>

--000000000000003c44062feccf05--