In what situations does the execution of a goroutine transfer control to other threads or tasks?

In Go, goroutines are lightweight threads scheduled by the Go scheduler. The execution of a goroutine can transfer control to other goroutines in the following situations:

• When calling the runtime.Gosched() function: explicitly hands over control to the scheduler, allowing other goroutines to run.
• During blocking operations: for example, waiting on a channel (<-chan), a mutex, a timer, or another synchronization primitive, the goroutine is blocked, and the scheduler switches to another.
• During system calls or I/O operations: if a goroutine is waiting for an operation to complete, the scheduler may switch.
• At the end of time slices: the Go scheduler can preempt the current goroutine and switch to another for fair CPU time distribution.

Thus, control switching occurs automatically by the Go scheduler and can also be explicitly invoked via runtime.Gosched() or during blocking.