Skip to content

Commit

Permalink
43
Browse files Browse the repository at this point in the history
  • Loading branch information
stephencelis committed Jan 16, 2019
1 parent 3892be4 commit 342950d
Show file tree
Hide file tree
Showing 13 changed files with 15 additions and 4 deletions.
2 changes: 1 addition & 1 deletion 0042-the-many-faces-of-flatmap-pt1/README.md
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
## [Point-Free](https://www.pointfree.co)

> #### This directory contains code from Point-Free Episode: [The Many Faces of Flat-Map: Part 1](https://www.pointfree.co/episodes/ep42-the-many-faces-of-flat-map)
> #### This directory contains code from Point-Free Episode: [The Many Faces of Flat-Map: Part 1](https://www.pointfree.co/episodes/ep42-the-many-faces-of-flat-map-part-1)
>
> Previously we've discussed the `map` and `zip` operations in detail, and today we start completing the trilogy by exploring `flatMap`. This operation is precisely the tool needed to solve a nesting problem that `map` and `zip` alone cannot.
Expand Down
3 changes: 0 additions & 3 deletions 0043-many-faces-of-flatmap-pt2/README.md

This file was deleted.

File renamed without changes.
14 changes: 14 additions & 0 deletions 0043-the-many-faces-of-flatmap-pt2/README.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,14 @@
## [Point-Free](https://www.pointfree.co)

> #### This directory contains code from Point-Free Episode: [The Many Faces of Flat-Map: Part 2](https://www.pointfree.co/episodes/ep43-the-many-faces-of-flat-map-part-2)
>
> Now that we know that `flatMap` is important for flattening nested arrays and optionals, we should feel empowered to define it on our own types. This leads us to understanding its structure more in depth and how it’s different from `map` and `zip`.
### Getting Started

* Clone repo
* `cd` into this directory
* Run `swift package generate-xcodeproj`
* Open `ManyFacesOfFlatMapPt2.xcworkspace`
* Build the package for _macOS_
* Open the playground

0 comments on commit 342950d

Please sign in to comment.