<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Go on Kailun's Blog</title><link>https://elated-hopper-5c0cb3.netlify.app/tags/go/</link><description>Recent content in Go on Kailun's Blog</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Mon, 01 Dec 2025 09:10:16 +0800</lastBuildDate><atom:link href="https://elated-hopper-5c0cb3.netlify.app/tags/go/index.xml" rel="self" type="application/rss+xml"/><item><title>Visualizing Go Scheduler Events at Runtime</title><link>https://elated-hopper-5c0cb3.netlify.app/posts/go-slowmo/</link><pubDate>Mon, 01 Dec 2025 09:10:16 +0800</pubDate><guid>https://elated-hopper-5c0cb3.netlify.app/posts/go-slowmo/</guid><description>&lt;p&gt;Being a Go dev for some time, my curiosity in Go&amp;rsquo;s runtime has been gradually built up to the point where I long for more mental grasp than roughly knowing a concept or two. With this in mind, I spent the past few months building &lt;a href="https://kailunli.me/go-slowmo"&gt;go-slowmo&lt;/a&gt;, some simple visualization around Go&amp;rsquo;s GMP scheduling model, which hopefully provides myself and others another way to look into that part of the Go runtime.&lt;/p&gt;</description></item><item><title>Wrapping up Fundamentals of Go Interface: Representation, Reflection and More</title><link>https://elated-hopper-5c0cb3.netlify.app/posts/go-interface/</link><pubDate>Fri, 31 Jul 2020 21:21:33 -0700</pubDate><guid>https://elated-hopper-5c0cb3.netlify.app/posts/go-interface/</guid><description>&lt;p&gt;Interface is, in many&amp;rsquo;s opinion, the shiniest part of the design of Go, and it adds flexibility to this statically typed language. As a noob gopher, I feel that leveraging interfaces does help deliver elegant and maintainable code. However, when not fully understood, interface might also be a great source of confusion. In this post, we will target some fundamental yet a bit complex part of Go interface, namely, its representation, its metaprogramming in reflection, and the role it plays in the new proposal of Go generics.&lt;/p&gt;</description></item></channel></rss>