Ville Saukkonen

@jevakallio Thanks for the contribution! I rerun the test suite and looks like there are bunch of valid errors too.

@matthargett feel free to fork and reopen the PR with fixed test cases. I'm afraid that the original author is no longer interested in this.

@jevakallio any progress? :)

There are two different ways of importing in libdefs: ``` import type { MyType } from 'some-module'; declare module 'other-module' { declare export function takesMyType(val: MyType): number; } ``` and...

There has been some work on moving flow-typed to lerna monorepo format so that libdefs could be published in NPM, which would also allow dependencies between libdefs: https://github.com/flow-typed/flow-typed/tree/v3-experimental It would...

If `flow-typed` moved to Lerna monorepo way of handling libdefs, how would you want the naming to be? In DefinitelyTyped libdefs are defined in package.json like: ``` { "dependencies": {...

@sehrope what is the purpose of using the pool in that case if you need to manage your connections by yourself?

I still don't understand. Why wouldn't I just use the regular connection to do that? How do I benefit of pool then?

So the sole benefit is to set max limit but it does not fully manage it? Why ``` const client = new pg.Pool(); client.query(); ``` works without `.connect()`, but with...

Is there a reason why pool.query _couldn't_ handle the query stream case? I tinkered a bit and found my self basically marrying query stream and connection handling in a way...