The Context API in Go has a fair bit of subtlety, yet it is an extensible and robust API capable of enabling correct distributed system design and making concurrency appear synchronous.
In this article, I analyze how the API's documentation has (regrettably) allowed for confusion to arise about where the API should and shouldn't be used, particularly when it comes to scopes in a program. To do this, we visit the historical and ancillary texts and explore some of the logical implications of various forms of use of the API as well as considerations of the language ecosystem and what requirements the API was trying to address.
Comments
The Context API in Go has a fair bit of subtlety, yet it is an extensible and robust API capable of enabling correct distributed system design and making concurrency appear synchronous.
In this article, I analyze how the API's documentation has (regrettably) allowed for confusion to arise about where the API should and shouldn't be used, particularly when it comes to scopes in a program. To do this, we visit the historical and ancillary texts and explore some of the logical implications of various forms of use of the API as well as considerations of the language ecosystem and what requirements the API was trying to address.