dmitriz / functional-examples

Examples with Functional JavaScript, following Professor Frisby's course

functional-examples

New functional library cpsfy

UPDATE. Check out my new advanced functional library: https://github.com/dmitriz/cpsfy

Examples with Functional JavaScript

Heavily annotated examples from the awesome videos Professor Frisby Introduces Composable Functional JavaScript, see also the discussion on Reddit and on Hacker News.

See also the wonderful e-book Professor Frisby's Mostly Adequate Guide to Functional Programming by the same author (See also https://github.com/MostlyAdequate/mostly-adequate-guide for the updates).

What makes Prof. Frisby's course and book awesome?

Both course and book amazingly manage to avoid suffering from the two widespread diseases when explaining abstract functional concepts:

• The first disease is to stay with abstract artifically simplified examples that can be easily manipulated directly without the theory, thus failing to illustrate the very benefits of the theory and abstraction. The reader not familiar with real world uses of that abstraction is therefore struggling to appreciate its usefulness.

• The second disease is to bring complete nontrivial real world examples relying on all technical details involved, including those not relevant to the point of the explanation. The reader not familiar with those technical details can feel distracted if not confused.

Professor Frisby masterfully manages to navigate the reader through convincing real world examples demonstrating real benefits of the functional abstractions with sharp focus and no distraction by unnecessary details.

Running Examples

Install the packages with either of

yarn install
npm install

then enter the examples directory and run the files directly with node

node <file.js>

Related Projects

• Monadic Libraries Examples with Tests

functional-examples's Issues

Action required: Greenkeeper could not be activated 🚨

🚨 You need to enable Continuous Integration on Greenkeeper branches of this repository. 🚨

To enable Greenkeeper, you need to make sure that a commit status is reported on all branches. This is required by Greenkeeper because it uses your CI build statuses to figure out when to notify you about breaking changes.

Since we didn’t receive a CI status on the greenkeeper/initial branch, it’s possible that you don’t have CI set up yet. We recommend using Travis CI, but Greenkeeper will work with every other CI service as well.

If you have already set up a CI for this repository, you might need to check how it’s configured. Make sure it is set to run on all new branches. If you don’t want it to run on absolutely every branch, you can whitelist branches starting with greenkeeper/.

Once you have installed and configured CI on this repository correctly, you’ll need to re-trigger Greenkeeper’s initial pull request. To do this, please click the 'fix repo' button on account.greenkeeper.io.

Dependency Dashboard

This issue lists Renovate updates and detected dependencies. Read the Dependency Dashboard docs to learn more.

Ignored or Blocked

These are blocked by an existing closed PR and will not be recreated unless you click a checkbox below.

• fix(deps): update dependency fluture to v14
• fix(deps): update dependency immutable to v4

Detected dependencies

npm

includes/package.json

• daggy 1.5.0
• futurize 1.2.0

package.json

• creed ^1.4.0
• data.either ^1.4.0
• data.task ^3.1.2
• fantasy-identities 0.0.1
• fluture ^11.0.3
• futurize ^1.2.0
• immutable ^3.8.2
• immutable-ext ^1.1.5
• request ^2.79.0

---

• Check this box to trigger a request for Renovate to run again on this repository

An in-range update of request is breaking the build 🚨

The dependency request was updated from 2.88.0 to 2.88.2.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

request is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Status Details

• ❌ AnyLint: They had a total of 1 failure, 495 warnings, and 29 notices.

Due to Github limitations, you will only see the first 50 annotations. Use https://anylint.hell.sh for a full report.

You may learn much more from a game you lose than from a game you win. You will have to lose hundreds of games before becoming a good player.

— José Raúl Capablanca

---

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

---

Your Greenkeeper Bot 🌴

Action required: Greenkeeper could not be activated 🚨

🚨 You need to enable Continuous Integration on Greenkeeper branches of this repository. 🚨

To enable Greenkeeper, you need to make sure that a commit status is reported on all branches. This is required by Greenkeeper because it uses your CI build statuses to figure out when to notify you about breaking changes.

Since we didn’t receive a CI status on the greenkeeper/initial branch, it’s possible that you don’t have CI set up yet. We recommend using Travis CI, but Greenkeeper will work with every other CI service as well.

If you have already set up a CI for this repository, you might need to check how it’s configured. Make sure it is set to run on all new branches. If you don’t want it to run on absolutely every branch, you can whitelist branches starting with greenkeeper/.

Once you have installed and configured CI on this repository correctly, you’ll need to re-trigger Greenkeeper’s initial pull request. To do this, please click the 'fix repo' button on account.greenkeeper.io.

Action required: Greenkeeper could not be activated 🚨

🚨 You need to enable Continuous Integration on Greenkeeper branches of this repository. 🚨

To enable Greenkeeper, you need to make sure that a commit status is reported on all branches. This is required by Greenkeeper because it uses your CI build statuses to figure out when to notify you about breaking changes.

Since we didn’t receive a CI status on the greenkeeper/initial branch, it’s possible that you don’t have CI set up yet. We recommend using Travis CI, but Greenkeeper will work with every other CI service as well.

If you have already set up a CI for this repository, you might need to check how it’s configured. Make sure it is set to run on all new branches. If you don’t want it to run on absolutely every branch, you can whitelist branches starting with greenkeeper/.

Once you have installed and configured CI on this repository correctly, you’ll need to re-trigger Greenkeeper’s initial pull request. To do this, please click the 'fix repo' button on account.greenkeeper.io.

An in-range update of fluture is breaking the build 🚨

The dependency fluture was updated from 11.0.1 to 11.0.2.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

fluture is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Status Details

• ❌ AnyLint: They had a total of 1 failure, 495 warnings, and 29 notices.

Due to Github limitations, you will only see the first 50 annotations. Use https://anylint.hell.sh for a full report.

You may learn much more from a game you lose than from a game you win. You will have to lose hundreds of games before becoming a good player.

— José Raúl Capablanca

---

Release Notes for Version 11.0.2

🐛 Fixes an issue where hook would attempt to dispose a resource twice if the disposal Future itself would cancel the hooked Future synchronously.

Commits

The new version differs by 9 commits.

• 07a1de9 Release 11.0.2
• 21f6181 Merge pull request #351 from fluture-js/avaq/hook-bug
• 8284c87 Merge pull request #348 from galileopy/readme-promise-approximation
• 933630a Fix hook disposing twice when cancelled during disposal
• 178b629 Improve README with more precise comparisons with Promises.
• 5ca8af4 Merge pull request #328 from fluture-js/greenkeeper/mocha-6.1.2
• 445a491 chore(package): update mocha to version 6.1.2
• c6c2097 Merge pull request #322 from fluture-js/greenkeeper/sanctuary-type-classes-11.0.0
• f9c2830 chore(package): update sanctuary-type-classes to version 11.0.0

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

---

Your Greenkeeper Bot 🌴