Bence Dányi

@jonathanong the problem is not that they are not readable, they are completely missing if they are not created in the right place (see my first example). Touching stack traces...

So it can't be solved without touching the stack trace :disappointed:... `bluebird` is definitely useful for development, thanks :+1:.

It has a huge performance impact _afaik_, and there should be meaningful stack traces in prod too.

Wow, I thought that long stack traces are much more slower than the native implementation. Thanks for the info :+1: !

> `co@4+` requires a `Promise` implementation. For versions of node `< 0.11` and for many older browsers, you should/must include your own `Promise` polyfill. So yeah, you should do `global.Promise...

Well, if you know that `foo` is a function, and in the source code (`foo.toString()`) you see that it accepts only a `cb` (or `callback`, etc) argument, then you can...

@ptgamr @dimitarkolev I'm not sure if this is till an issue for you guys, but I create watermarked images with this pattern: ``` js gm(source) .command('composite') .gravity('SouthEast') .out('-geometry', '+20+10') //...

it's a bit annoying, but if you use `babel` for transpiling, you cannot use the `@@iterator()` syntax :crying_cat_face:

in this case: https://flow.org/try/#0C4TwDgpgBAkgJlAvFAPAFQHwAo0EokZRoDcAUAMYD2AdgM7BQCWcAXLAsutgB5t58Eo3MqSzMsARlxtqAVwC2AIwgAnXGTFwsAcgBmlStulR6KxtQDm6oA ```js type Id = (T) => T; const id: Id = (x: T): T => x; (id(1): number); (id('foo'): string); ```

@robertmassaioli I took the example from the spec, so I think it's valid (sure, the `other.json` reference is external, which isn't supported, and that is fine) The `#item` reference in...