Some question about executor and golang

[kysshsy]

I found

gocron/executor.go

Line 110 in 560e7b9

e.stopCh <- struct{}{}

it sends a value to buffered channel

gocron/executor.go

Line 111 in 560e7b9

<-e.stopCh

next line, it read from the same buffered channel.
Is it possible that it reads the value it sends and the executor doesn't stop.
Is this a golang skill(trick) ?

excuse my poor english

[JohnRoesler]

The write on line 110 is ready by the channel read on line 100:

gocron/executor.go

Lines 100 to 105 in 560e7b9

	case <-e.stopCh:
	cancel()
	runningJobsWg.Wait()
	e.stopCh <- struct{}{}
	return
	}

To my knowledge it couldn't read on line 111 before the 110 write was ready by 100. 111 then waits for the write on 103.

We'd have to dig deeper into how channels / goroutines work to understand if its possible if say one of the gorouintes is running much slower and that causes some out of sync issues.

[kysshsy]

thanks for your help