GoKawiil
Tech News
Following discussions at RustConf's Unconf event, developer Russell has begun drafting a living document of best practices for writing performant applications on Tokio's async runtime. The post outlines general principles, emphasizing that performance issues are highly context-dependent and that developers should first confirm a real problem exists before optimizing.
A research paper titled 'A Design Space Exploration of Async/Await' tested a simple fire-and-forget logging program across seven modern async runtimes and found four distinct output patterns. The authors report that across three variations of the same small program, no two runtimes ever produced identical results, despite all using the same async/await keywords.
A programming-theory essay pushes back on the claim that any threaded function argument, such as Go's context.Context, qualifies as a 'function color' like async/await. The author argues that if every parameter counted as a color, the concept wouldn't have needed inventing decades after functions themselves existed, and proposes analyzing coloring instead as a question of how a change to one function propagates through the call graph to its callers.