golang/go

x/website/_content/tour: explain the semantics of the main goroutine

Open

#13,750 opened on Dec 28, 2015

View on GitHub
 (1 comment) (0 reactions) (0 assignees)Go (19,008 forks)batch import
DocumentationNeedsInvestigationhelp wanted

Repository metrics

Stars
 (133,883 stars)
PR merge metrics
 (No merged PRs in 30d)

Description

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.

Contributor guide

Research direction
Investigate the behavior of the main goroutine and how it exits, and update the tour text to clarify that the program exits when the main goroutine ends, not when all goroutines finish.
Tech stack
go
Domain
documentation
Issue type
Documentation
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
1
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Under 1 hour
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Mostly clear
Prerequisites
Go basics
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
85