Amir Amazigh BOUBEKKI

I think `multiprocessing-logging` should be activated when the handler is not socket based.

It's ok I can wait.

FWIW, I am not interested in `yield`. The only thing I need is the ability to declare a lambda `async` and call another lambda with `await`. Hope that helps.

In BiwaScheme, I use a biwascheme primitive that rely on call/cc. In Javascript, I use `async`/`await`. FWIW [here](https://github.com/amirouche/socialite/blob/master/frontend/src/forward.js#L19) is the code that converts the async function into regular callback style...

In BiwaScheme, I use a biwascheme primitive that rely on call/cc. In Javascript, I use `async`/`await`. FWIW [here](https://github.com/amirouche/socialite/blob/master/frontend/src/forward.js#L26) is the code that converts the async function into regular callback style...

`async` / `await` keywords are a language design mistake. It is better to have async without keywords.

I stumbled upon the issue while looking up what is related to wasm and Scheme. > Once [Racket compiles to Chez] getting racket compiling to wasm should be relatively straightforward...

Quoting https://github.com/grpc/grpc/issues/20194#issue-490393542: > In order for an API to integrate into a foreign event loop, it needs to provide a polling interface as well as a callback function which can...

Very interesting. @edholland can you recommend a ddb emulator to help with the dev setup, and CI?

This is available in ee edition, see the directory `ee/` Closing duplicate the feature is already implemented.