Skip to content

Commit

Permalink
Improves vector field case study
Browse files Browse the repository at this point in the history
  • Loading branch information
evhub committed Feb 5, 2016
1 parent b7fb233 commit 96a24f0
Showing 1 changed file with 6 additions and 7 deletions.
13 changes: 6 additions & 7 deletions HELP.md
Original file line number Diff line number Diff line change
Expand Up @@ -22,8 +22,7 @@
1. [`diagonal_line`](#diagonal_line)
2. [`linearized_plane`](#linearized_plane)
3. [`vector_field`](#vector_field)
4. [`magnitude_field`](#magnitude_field)
5. [Applications](#applications)
4. [Applications](#applications)
7. [Filling in the Gaps](#filling-in-the-gaps)

<!-- /MarkdownTOC -->
Expand Down Expand Up @@ -715,20 +714,20 @@ _Hint: Remember, the way we defined vector it takes the components as separate a
<br>
<br>

We're making good progress! Before we move on, check your solution against mine:
```
def vector_field() = linearized_plane() |> map$((xy) -> vector(*xy))
```
All we're doing is taking our `linearized_plane` and mapping `vector` over it, but making sure to call vector with each element of the tuple as a separate argument.

### `magnitude_field`
### Applications

iterator slicing

```
def magnitude_field() = vector_field() |> map$(abs)
```

### Applications

iterator slicing

## Filling in the Gaps

lazy lists, function composition, implicit partial, backwards pipes

0 comments on commit 96a24f0

Please sign in to comment.