Skip to content

Commit

Permalink
Merge pull request #75 from MrBenJ/fix/gender-and-set
Browse files Browse the repository at this point in the history
Fix/gender and set
  • Loading branch information
MrBenJ committed Mar 22, 2019
2 parents 84004fa + 9b98764 commit 73c9054
Show file tree
Hide file tree
Showing 5 changed files with 11 additions and 6 deletions.
1 change: 1 addition & 0 deletions README.md
Expand Up @@ -81,3 +81,4 @@ This book would not have been possible for the several contributors that have gr
* [rw251](https://www.github.com/rw251) - Proofreading
* [jessmear](https://www.github.com/jessmear) - Proofreading and content suggestion
* [pauldariye](https://www.github.com/pauldariye) - Proofreading and example edits
* [marwahaha](https://www.github.com/marwahaha) - Proofreading and fixing misinformation on `Set`
9 changes: 5 additions & 4 deletions book/003-complex-data-types.md
Expand Up @@ -261,12 +261,13 @@ Under the hood, if an object has no more references pointing to it, it will be c

# Set and WeakSet

Set and WeakSet are identical to Map, except for 2 major differences:
Set and WeakSet are identical to Map, except for a few major differences:

1. Instead of `.set` for values, you use `.add()` to create a key value pair to store.
2. All values in a `Set` must be unique and only occur once.
1. `Set` is a store of just `values` - not `key-value pairs` like in `Map`.
2. Instead of `.set` for values, you use `.add()` to store a value.
3. All values in a `Set` must be unique and only occur once.

As far as everything else, they are very identical and are ordered.
As far as everything else, they are very identical, including being **ordered by insertion**.

If you need a `Map`-like storage or cache, but all values must be unique, then `Set` is *perfect*!

Expand Down
2 changes: 1 addition & 1 deletion book/008-Modern-JS-Architecture.md
Expand Up @@ -23,7 +23,7 @@ There's 3 major aspects of a modern front end system:

# Task runners

Back in the ancient JavaScript civilizations of 2013, brave warrior and huntress tribes of developers used `grunt` to start automating repetitive and menial tasks.
Back in the ancient JavaScript civilizations of 2013, brave tribes of developers used `grunt` to start automating repetitive and menial tasks.

With the advent of Node.js, there were more and more tools that started appearing in the JavaScript ecosystem. We were able to use the command line to:

Expand Down
3 changes: 3 additions & 0 deletions src/pages/index.js
Expand Up @@ -79,6 +79,9 @@ const IndexPage = (): Node => {
<li>
<a href="https://www.github.com/pauldariye" target="_blank" rel="noopener noreferrer">pauldariye</a> - Proofreading and example edits
</li>
<li>
<a href="https://www.github.com/marwahaha" target="_blank" rel="noopener noreferrer">marwahaha</a> - Proofreading and fixing misinformation on Set.
</li>
</ul>
</Layout>
);
Expand Down
2 changes: 1 addition & 1 deletion stylesheet.css
Expand Up @@ -627,7 +627,7 @@ pre tt:after {
.container {
position: relative;
margin: 0 auto;
max-width: 992px;
max-width: 680px; /* For typograpy! */
padding: 0px 1.0875rem 1.45rem;
padding-top: 0;
}
Expand Down

0 comments on commit 73c9054

Please sign in to comment.