Fabricio Matte

Looks like I got a bit carried away fixing some nits in the process. Let me know if you would prefer to have split commits or PRs for those.

Thanks. :smile_cat:

I'll write the tests before merging, I'd feel bad lowering a project's code coverage.

Isn't it possible/viable to compile especially with Babel using the [`runtime` transformer](http://babeljs.io/docs/usage/runtime/) and ship a browserified bundle?

Agree. But I guess you mean either: ``` js import { Invoke } from 'especially/abstract-operations'; ``` Or: ``` js import Invoke from 'especially/abstract-operations/invoke'; ``` I would favor the first approach,...

> I think it's probably best to just skip that part (maybe leaving a to-do). Sounds good to me. So, can we assume that everything belongs to the same domain...

It is possible to compile `especially` to ES5 using `babel@6`, then it should run in browsers. In my experience, this has been working fine so far. Perhaps we can even...

Sure, I have other priorities at the moment but may get to it sometime. Or we can delegate this to the consumers: most people consuming this package for such use...

Perhaps `goiabada.test` could accept an async function as argument, then you can just `await` inside the callback. E.g.: ``` js goiabada.test(async assert => { assert.ok(await someAsyncFunction(), "it works!"); }); ```...

It would be nice to consider some real (yet simple) async test use cases. This way, it would be easier to discuss which syntax better fits real use cases, and...