~samhh/writings

ec87ace99c2ce679954905a0cbb8af8da3ad8579 — Sam A. Horvath-Hunt 3 years ago c71756d
Update js-fp-jargon (self-hosting)
1 files changed, 1 insertions(+), 7 deletions(-)

M published/20200330-js-fp-jargon.md
M published/20200330-js-fp-jargon.md => published/20200330-js-fp-jargon.md +1 -7
@@ 116,9 116,7 @@ const f = async (x: string): Promise<number> => {
};
```

Before we move on, if you were wondering why JavaScript's promise isn't a proper functor or monad, here's the legacy of that unfortunate decision:

{% github https://github.com/promises-aplus/promises-spec/issues/94#issuecomment-16176966 %}
Before we move on, if you were wondering why JavaScript's promise isn't a proper functor or monad, [here's](https://github.com/promises-aplus/promises-spec/issues/94#issuecomment-16176966) the legacy of that unfortunate decision.

It hasn't aged particularly well. This also happens to be whence the [fantasy-land](https://github.com/fantasyland/fantasy-land) specification derived its name.



@@ 266,7 264,3 @@ traverseOptArr([some(5), none],     option.map(x => x * 2)) // none

Just like with sequencing, this will short-circuit if the type we're inverting is already in its failure state.

---

I hope that's helpful to some of you reading. Let me know in the comments if there's anything in particular you'd like to see addressed that's missing.