On 8 March 2025 21:42:21 GMT, Daniil Gentili <daniil.gent...@gmail.com> wrote:
>
>To make an analogy, it's like saying PHP should have an io {} block, that 
>makes sure all file resources opened within (even internally, 10 stack levels 
>deep into 3 libraries, whose instances are all used after the io {} block) are 
>closed when exiting.

Traditional PHP offers exactly this: the SAPI lifecycle tracks all file handles 
opened within a request, and closes them cleanly before reusing the thread or 
process for another request. Essentially what I'm proposing is a way to 
implement the same isolation in userland, by marking a checkpoint in the code.

As I've said repeatedly, it doesn't necessarily need to be a mandatory 
restriction, it can be a feature to help users write code without having to 
worry about *accidentally* leaving a background fiber running. 

Rowan Tommins
[IMSoP]

Reply via email to