> I have believed for a long time that goroutines (which can be
> implemented on top of SRFI 18) are in some sense the Right Thing.  See
> <http://wiki.call-cc.org/eggref/5/gochan>.  That way you can get
> shared-almost-nothing (with some self-discipline) with the intra-process
> analogue of pipes, which are a very nice way to provide concurrency.

BTW, since you like that stuff you might enjoy designing a Scheme
equivalent for Python's ASGI (an asynchronous version of the venerable
WSGI abstraction). It's for next generation HTTP which features stream
multiplexing in-protocol, but the abstraction is more generic than just
HTTP.

Here's how its applications look:
<https://github.com/simonw/asgi-cors/blob/master/asgi_cors.py>. If you
start reading at the line "async def app_wrapped_with_cors(scope,
recieve, send):" (yes, Python has an async keyword now) you'll note that
the HTTP request handler function gets "receive" and "send" procedures
that it can call at will. This is by contrast with the synchronous WSGI
in which the handler just got a request object and returned a response
object.

I've promised to write a SRFI about a synchronous WSGI equivalent soon,
with assistance from Peter and Arthur, but I'll gladly leave the more
complex asynchronous version to someone who enjoys concurrent stuff :)