Goroutines & Concurrency interview questions

1. A.a lightweight function execution started with the go keyword and multiplexed onto OS threads by the runtime
2. B.the setting that limits how many operating-system threads may execute user code simultaneously
3. C.the runtime component that maps goroutines onto threads using per-processor run queues that steal tasks when idle
4. D.the classic bug where goroutines in a range loop all observed the same shared iteration variable before per-iteration scoping was added

Answer + AI explanation with Pro

1. A.GOMAXPROCS
2. B.WaitGroup
3. C.Goroutine
4. D.Loop variable capture (pre-1.22)

Answer + AI explanation with Pro

1. A.Goroutine — a lightweight function execution started with the go keyword and multiplexed onto OS threads by the runtime
2. B.Goroutine — the runtime component that maps goroutines onto threads using per-processor run queues that steal tasks when idle
3. C.Goroutine — a sync counter whose Add, Done and Wait methods block until a set of goroutines has finished
4. D.Goroutine — the setting that limits how many operating-system threads may execute user code simultaneously

Answer + AI explanation with Pro

1. A.the runtime component that maps goroutines onto threads using per-processor run queues that steal tasks when idle
2. B.the classic bug where goroutines in a range loop all observed the same shared iteration variable before per-iteration scoping was added
3. C.a sync counter whose Add, Done and Wait methods block until a set of goroutines has finished
4. D.the setting that limits how many operating-system threads may execute user code simultaneously

Answer + AI explanation with Pro

1. A.WaitGroup
2. B.Work-stealing scheduler
3. C.Loop variable capture (pre-1.22)
4. D.GOMAXPROCS

Answer + AI explanation with Pro

1. A.GOMAXPROCS — a sync counter whose Add, Done and Wait methods block until a set of goroutines has finished
2. B.GOMAXPROCS — a lightweight function execution started with the go keyword and multiplexed onto OS threads by the runtime
3. C.GOMAXPROCS — the setting that limits how many operating-system threads may execute user code simultaneously
4. D.GOMAXPROCS — the classic bug where goroutines in a range loop all observed the same shared iteration variable before per-iteration scoping was added

Answer + AI explanation with Pro

1. A.the classic bug where goroutines in a range loop all observed the same shared iteration variable before per-iteration scoping was added
2. B.the runtime component that maps goroutines onto threads using per-processor run queues that steal tasks when idle
3. C.the setting that limits how many operating-system threads may execute user code simultaneously
4. D.a sync counter whose Add, Done and Wait methods block until a set of goroutines has finished

Answer + AI explanation with Pro

1. A.GOMAXPROCS
2. B.Work-stealing scheduler
3. C.Goroutine
4. D.WaitGroup

Answer + AI explanation with Pro

1. A.Work-stealing scheduler — the classic bug where goroutines in a range loop all observed the same shared iteration variable before per-iteration scoping was added
2. B.Work-stealing scheduler — the runtime component that maps goroutines onto threads using per-processor run queues that steal tasks when idle
3. C.Work-stealing scheduler — the setting that limits how many operating-system threads may execute user code simultaneously
4. D.Work-stealing scheduler — a lightweight function execution started with the go keyword and multiplexed onto OS threads by the runtime

Answer + AI explanation with Pro

1. A.the setting that limits how many operating-system threads may execute user code simultaneously
2. B.the runtime component that maps goroutines onto threads using per-processor run queues that steal tasks when idle
3. C.a lightweight function execution started with the go keyword and multiplexed onto OS threads by the runtime
4. D.a sync counter whose Add, Done and Wait methods block until a set of goroutines has finished

Answer + AI explanation with Pro

1. A.Work-stealing scheduler
2. B.Loop variable capture (pre-1.22)
3. C.Goroutine
4. D.WaitGroup

Answer + AI explanation with Pro

1. A.WaitGroup — a lightweight function execution started with the go keyword and multiplexed onto OS threads by the runtime
2. B.WaitGroup — a sync counter whose Add, Done and Wait methods block until a set of goroutines has finished
3. C.WaitGroup — the classic bug where goroutines in a range loop all observed the same shared iteration variable before per-iteration scoping was added
4. D.WaitGroup — the setting that limits how many operating-system threads may execute user code simultaneously

Answer + AI explanation with Pro

1. A.the setting that limits how many operating-system threads may execute user code simultaneously
2. B.the classic bug where goroutines in a range loop all observed the same shared iteration variable before per-iteration scoping was added
3. C.the runtime component that maps goroutines onto threads using per-processor run queues that steal tasks when idle
4. D.a sync counter whose Add, Done and Wait methods block until a set of goroutines has finished

Answer + AI explanation with Pro

1. A.Goroutine
2. B.Loop variable capture (pre-1.22)
3. C.GOMAXPROCS
4. D.WaitGroup

Answer + AI explanation with Pro

1. A.Loop variable capture (pre-1.22) — a lightweight function execution started with the go keyword and multiplexed onto OS threads by the runtime
2. B.Loop variable capture (pre-1.22) — the classic bug where goroutines in a range loop all observed the same shared iteration variable before per-iteration scoping was added
3. C.Loop variable capture (pre-1.22) — a sync counter whose Add, Done and Wait methods block until a set of goroutines has finished
4. D.Loop variable capture (pre-1.22) — the setting that limits how many operating-system threads may execute user code simultaneously

Answer + AI explanation with Pro