Well, I already thought that my suggestion seems somewhat too simple… :) I agree, if a fatal error occurs within a goroutine but you don’t want to crash the whole process from within this goroutine (or even from within the library), then error channels seem the way to go.
> Am 08.02.2017 um 11:04 schrieb Francis Chuang <[email protected]>: > > I made a mistake with my example. c.Start() needs to be a separate go routine > because it is an infinite loop waiting for messages: go c.Start(). > > In that case, I am guessing an errors channel would be the best? > > Cheers, > Francis > > -- > You received this message because you are subscribed to a topic in the Google > Groups "golang-nuts" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/golang-nuts/zssLR41Kk3Q/unsubscribe > <https://groups.google.com/d/topic/golang-nuts/zssLR41Kk3Q/unsubscribe>. > To unsubscribe from this group and all its topics, send an email to > [email protected] > <mailto:[email protected]>. > For more options, visit https://groups.google.com/d/optout > <https://groups.google.com/d/optout>. -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
