Geoffrey

Sadly, my screenshot was not the most minimal example and I noticed other instances where it looks really off. The last line looks OK but every other case has kerning...

I do this kind of stuff all the time: ```js test('detect when the player has won', t => [ { player: 'scissors', computer: 'paper' }, { player: 'paper', computer: 'rock'...

I often have the opposite problem and would prefer to read `{ [K in keyof Person]: never }` or even `{ age: never, name: never }` over `Mapped` because those...

Hi matthew-dean, Thanks a lot for your feedback. Despite my best efforts I was indeed a bit expeditious in some places and I am relatively blind to what needs to...

Regarding your use case, I am not certain free-types are necessary. Could you be more precise or link to a stackoverflow question?

People have weird expectations regarding HKT and it is not clear what you need to do, so I am testing the water ;) You can find bellow an example derived...

I notice that your interface and functionality is becoming more and more similar to [free-types](https://github.com/geoffreytools/free-types) although the underlying implementation is very different. I am considering abandoning this project considering how...

Hi, The only way I can imagine implementing this would be to create a type definition from `Haystack` with a union of every possible path. This would likely tank performance....

Hum I actually tried a dummy interface with an exhaustive union of paths and you wouldn't get auto-completion with this. You would get suggestions in a very noisy tooltip but...

You may be interested in `FindPaths` for quickly coming up with a path. It's been added to the latest version. I updated the readme.