this:
res := make(chan []string)
go func() {
res <- slowSearch(from, to)
close(res)
}()
and in next step, it will wait for cahnnels in a select:
// wait for 2 events: either of one will be the result
for {
select {
case dst := <-res:
return dst, nil
case <-ctx.Done():
return []string{}, ctx.Err()
}
}
So when <-ctx.Done() going to have any message, it will return our function return []string{}, ctx.Err().
My question is: after canceling the context and return from Search, the main problem is our goroutine is still running in the background!
for example, the slowSearch() takes 17 seconds to write result into our res channel. and our context timeout is (for example) 3 seconds.
Now after Search() reaching the timeout, our context will be canceled, and Search() will be returned.
But slowSearch() still running in backgroun for 17 seconds!
What should we do in this case?
Pass the parent context to slow search, there you also listen for its cancellation, that way it won't have to stay around doing nothing!
there’s no way to kill a goroutine, so you must write slowSearch in such a way that it respects a cancalable context. slowSearch must check whether the context was canceled and return ASAP
slowSearch() can do one thing at same time Either wait for context to be canceled, or doing its own job! My problem is here
what? I don’t understand
why can’t you make it check the context?
https://play.golang.org/p/U4yngByhKTS
ehm… why default in select?
Обсуждают сегодня