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

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

wants to merge 1 commit into from

Conversation

sbinet
Copy link
Member

@sbinet sbinet commented Feb 12, 2016

No description provided.

@@ -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).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants