Hi! I m not sure to get why you say 2-4 is not worthy.
Is it because it seems there is no generic implementation of such behavior ? Which leads to costly copy pastes. Or some side effects that may occur and which make it to difficult to maintain to even attempt to write it ? I made a new version based on your pseudo code, https://gist.github.com/mh-cbon/9eb7701e57a8f37bb7e62647dc9726e8 I slightly changed it to well split checker / producer. i have in mind sometimes soon i ll want to load some data from a storage which is not a FS. I also added the notion of StrategyDeliverer, because there could be some behaviors to modify when an existing result become temporary invalid. There is no more registry shared across goroutines, the drawback is that for each result to be produced it needs to create N chans, N goroutines, ect. I don t have enough experience to say how bad this could be, I m little worried by contentions or other side effects i m not yet aware of because of the previous. Its still a long way to go : ) -- 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.
