That's a tough one. If your interviewer is an excellent engineer without an ego, you may want to point out that it might be better to keep concurrency and data structures separated. Perhaps you could even tell the story of the deprecated Java Vector class.
If your interviewer want you to show that you're familiar with mutexes, you may want to do something along these lines: http://yourbasic.org/golang/mutex-explained/ On Sunday, April 8, 2018 at 7:37:26 AM UTC+2, Xen wrote: > > Hi everyone, I have this mock interview question, "How would you implement > concurrent and blocking stack and queue in Go?" which I have no idea on how > to answer it. If anyone can guild me > -- 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.