I understand that the title might be somewhat confusing as Go is generally known for having good built-in support for concurrency. However, I don’t necessarily think it’s easy to write concurrent…

DevGenius serves as a platform for sharing insights and experiences in software development, offering articles and interviews with industry experts to gain  insights into various aspects of software engineering. By exploring DevGenius's curated content, developers can learn from real-world experiences, best practices, and lessons learned from seasoned professionals across different domains of software development. Whether you're looking for career advice, technical insights, or inspiration for your next project, DevGenius provides a  knowledge and expertise to help you succeed in your software development journey.

Dev Genius

Go is generally known for having good built-in support for concurrency in Go. The solution was fixed in #2171 by using sync. It could also have been fixed without using the sync package by using an init function to set the variable v once. When the doSomething function is evaluated, running RLock / RUnlock will not affect the original lock in the User struct rendering it useless. The solution uses a pointer.

Concurrency in Go is hard