Skip to content

tour: explain the semantics of the main goroutine #13750

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

Jump to bottom
Open
neelvirdy opened this issue Dec 28, 2015 · 1 comment
Open

tour: explain the semantics of the main goroutine #13750

neelvirdy opened this issue Dec 28, 2015 · 1 comment
Labels
Documentation Issues describing a change to documentation. help wanted NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one.
Milestone
Unreleased

Comments

@neelvirdy
Copy link

Context: http://127.0.0.1:3999/concurrency/1

In concurrency/1 (Goroutines), commenting out line 17 say("hello") also stops the go say("world") from doing anything. The program exits before any worlds are said, yet without commenting out line 17 it seems to wait for all goroutines to finish before exiting.
@bradfitz bradfitz added the Documentation Issues describing a change to documentation. label Jan 21, 2016
@bradfitz bradfitz added this to the Unreleased milestone Jan 21, 2016
@adg adg changed the title tour: goroutine relies on main thread call tour: explain the semantics of the main goroutine Jan 21, 2016
@gopherbot
Copy link
Contributor

CL https://golang.org/cl/35112 mentions this issue.

@adg adg removed their assignment Feb 14, 2018
@seankhliao seankhliao added the NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one. label Jul 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Documentation Issues describing a change to documentation. help wanted NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one.
Projects
None yet
Milestone
Unreleased
Development

No branches or pull requests
5 participants
@bradfitz @neelvirdy @adg @gopherbot @seankhliao