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.

Sign up for GitHub

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

2015/intro_concurrency: typo #8

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

2015/intro_concurrency: typo #8

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
2 changes: 1 addition & 1 deletion 2015/intro_concurrency.slide
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -82,7 +82,7 @@ Go is easy (language design):
- Simple syntax (discussed later)
- Garbage collected (no manual memory management)
- Stack traces on nil dereference (not "segmentation fault")
- Pointers but automatically on stack wherever possible
- Pointers put automatically on stack wherever possible
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think I meant the "but" originally, but it's a bad sentence. What really should be said here is that there are pointers, but you don't need to worry about them being heap allocated or stack allocated (they can't disappear on you).

- Composition of types, not inheritance
- Consistent design - legible code
- Large standard library
Expand Down