You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The logic works because I guess, starting goroutines usually runs a bit later than the code following the goroutine launch. This is / should be an implementation detail of Go's runtime and should not be relied on. Who knows if on a slower processor or busier system these are executed in different order.
The text was updated successfully, but these errors were encountered:
These things happen in chronological order:
incomingProcessor()
andoutgoingProcessor()
are started as goroutines (which stop ifznp.started == false
)The logic works because I guess, starting goroutines usually runs a bit later than the code following the goroutine launch. This is / should be an implementation detail of Go's runtime and should not be relied on. Who knows if on a slower processor or busier system these are executed in different order.
The text was updated successfully, but these errors were encountered: