I’m not sure what your goal is with this SRFI.  Could you clarify?

SRFI-18 (Multithreading support) is supported by many Scheme implementations and is the best thread API if you are interested in portability accross Scheme implementations.  It seems some of the things you are proposing have a direct link with SRFI-18 features, so I don’t understand why a new SRFI is needed.

Marc

> On May 6, 2021, at 6:28 AM, Amirouche <xxxxxx@hyper.dev> wrote:
>
> On 2021-05-05 20:30, Amirouche wrote:
>> I started to implement a Concurrent ML (CML) and read about the actor model
>> as part of Gambit termite library.
>
> Another thing to read would be trio, in particular:
>
>  https://trio.readthedocs.io/en/stable/design.html#exceptions-always-propagate
>
> Speaking of Python, I think the keywords async and await
> are a major roadblock to mainstream adoption of async.
> Those are not sufficient nor necessary to avoid errors.
>
> Also the related reading list:
>
>  https://github.com/python-trio/trio/wiki/Reading-list
>
> Another interesting source of information might be:
>
>  https://openjdk.java.net/projects/loom/
>
> Most of it has prior art...
>
>> Checkout the short preliminary SRFI at
>> https://github.com/pre-srfi/coop#specification
>
> I removed coop-priority procedure, see:
>
>  https://github.com/pre-srfi/coop/commit/999b208baaa3a2a878c3b57189f188cd123e7c85
>