Sam Whited <s...@samwhited.com> writes: > More opinions on the best way to do this would still be welcome, of > course. Thanks!
I've personally found that when designing an API, it's generally better to consider two things that are almost but not quite the same as two things (or, two endpoints if you prefer). To me, the combination of the callback rarely being needed and also not wanting to appear as if you're explicitly supporting more than one callback being specified makes a strong case for having two things exposed to the user (even if one is implented in terms of the other on your end). -- 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.
