Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Adjust section headers to avoid code #42

Merged
merged 1 commit into from
Apr 10, 2015
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions _posts/2015-04-10-Fearless-Concurrency.md
Original file line number Diff line number Diff line change
Expand Up @@ -422,7 +422,7 @@ access(&mut guard)

Disaster averted.

### Thread safety and `Send`
### Thread safety and "Send"

It's typical to distinguish some data types as "thread safe" and
others not. Thread safe data structures use enough internal
Expand Down Expand Up @@ -473,7 +473,7 @@ compiler will say:

Disaster averted.

### Sharing the stack: `scoped`
### Sharing the stack: "scoped"

So far, all the patterns we've seen involve creating data structures
on the heap that get shared between threads. But what if we wanted to
Expand Down