Giulio Canti

> Is there any counter example @mlegenhausen I haven't found one so far

btw there's no need for a new API ```ts import { Either } from 'fp-ts/Either' import { identity, Predicate, Refinement } from 'fp-ts/function' declare const fromPredicate: { (refinement: Refinement, onFalse:...

Also, the same trick could be applied to any API using a `Refinement` I guess: ```ts import { Either, getFilterable } from 'fp-ts/Either' import { Predicate, Refinement } from 'fp-ts/function'...

IMO we should deprecate `sequenceS` in favour of `apS` / `apSW`

> The JsonRecord type currently allows you to access any string key, but this isn't type safe IIRC there's a `tsconfig` option for that (`noUncheckedIndexedAccess`)

@ryota-ka @samhh thanks for your suggestions, just released `[email protected]` (`npm i fp-ts@next`), let me know if it's working as expected

@ENvironmentSet amazing trick, thanks for sharing > On the other hand this new encoding could help us dramatically reduce constraints on instance constants - we could drop URI field at...

@raveclassic the following snippet compiles too ```ts function lift(F: Functor1): (f: (a: A) => B) => (fa: Kind) => Kind { return (f) => (fa) => 'WAT' } ```

@brettmitchelldev thanks, I'm a bit lost, could you please provide an example containing: - the type-class `Functor` - Functor instances for `Option` and/or `Either` - the `lift` function above

If you are filtering (unlike mapping) you can get less entries, returning `Record` is not safe