Irakli Gozalishvili

So I'm clueless to what is going on, only other thing worth noting is that I have flow installed through `flow-bin` package which creates `/usr/local/bin/flow` symlink: ``` sh readlink /usr/local/bin/flow...

After digging further into it I realized that flow-bin is node-wrapper that uses actual `flow` binary bundled with it under `vendor/flow`. I have updated my flow path to `/usr/local/lib/node_modules/flow-bin/vendor/flow` which...

BTW changes I made originally did not turn out to be necessary after fixing the path.

I guess easier way to see this issue is by looking at https://astexplorer.net/#/8hK2Y2BwqI

I have run into the same problem, and also find handling of arrays surprising. I have identified problem to be caused by https://github.com/avajs/ava/blob/f5caa8fb823e369517053181494374c64dfa58b2/lib/like-selector.js#L4 Which I was able to address locally...

While we're at it I would also like to propose to remove `Iterable` from the `FileContent` because: It introduces this ambiguity when it comes to choosing right strategy. Which is...

> 1. The loss of very strong checking of the bytes at each point along a chain of libraries - the fact of having to parse the bytes or string...

To elaborate on my different tradeoffs comment. I think there two different approaches to abstractions / modularity: 1. Interfaces: Encode interaction API. 💚 Enables an implementation agnostic interface with components....

On type check not catching errors at runtime. - unit tests aren’t going to catch users passing invalid types at runtime either. - hand written parsers at every layer is...

> @Gozala in terms of implementation, this is going to mean we have a big fat interfaces library we all depend on? Or do each of these pieces get their...