Is there any drawbacks if we put the CancelFunc of a cancellable context.Context inside it's values?
Problem: I needed a cross breed of WaitGroup and Context. So a WaitGroup and it's CancelFunc is put inside it's values and are used with some helper functions. I wrote a variant of WaitGroup - with some needed features - but I see this pattern of accepting an argument like "ctx context.Context" as the first argument in functions. So I though it might be more idiomatic to use the Context instead. Any thoughts/suggestions? -- 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 golang-nuts+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
