• setInterval equivalent using multiple continuations or enable in background.
• throttled continuations
• debounced continuations

Not sure yet what their apis will look like as operations.

When wondering why there were failing checks, I looked and saw that we still had the CircleCI webhook enabled. After disabling that webhook and check, I noticed we still have a couple things to do:

1. It looks like we're doing both branch and pr builds. This is good, but shouldn't we be only doing one build per platform? Ideally we would do branch builds, but with the the merge commit so

Currently the tests are all in folders pos and neg.

Instead, we could organize them by topic:

• syntax
• handlers
• stdlib
• ...

and add additional README.md files to the folders guiding newcomers. Additionally, the tests could have comments explaining the features.

This way we could have a low cost documentation that is automatically checked

For instance, this should fail

(let {x 10 x 10} x)

• Enable the skip test added at 5255f43

problem

generated symbols are at risk of collision

'use effects'
try{
  const result = perform ({type : 'effect'});
  console.log(result);
} handle default with (e) {
  const handler = "GOTCHA"
  recall handler;
}

generates:

    *[__defaultEffectHandler__](e, resume) {
      const result = yield function (handler) {
        return new Promise(async (res, rej)