What is the value of building something like that into the language? Why <i>should</i> a language have a &quot;queue pattern&quot; built into the language itself? Go has to have channels as a primitive to be usable in 2015 because its lack of generally-accepted features makes it impossible to do the same in userland. Same with its lists, same with its maps. I don&#x27;t need it built into C++ or Scala or Java&#x2F;Kotlin or C# or D, because these languages aren&#x27;t unwilling to let me do it myself (but in all cases there are standard libraries to help me do it, even in the cases where it is not expressly already available).<p>You are implicitly casting as something to be praised one of the greater missteps of Go.