<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Abstraction on Mi&amp;Bee Blog</title><link>https://blog.mickeyzzc.tech/en/tags/abstraction/</link><description>Recent content in Abstraction on Mi&amp;Bee Blog</description><generator>Hugo -- gohugo.io</generator><language>en</language><managingEditor>蓝宝石的傻话</managingEditor><lastBuildDate>Thu, 12 Feb 2026 10:00:00 +0800</lastBuildDate><atom:link href="https://blog.mickeyzzc.tech/en/tags/abstraction/rss.xml" rel="self" type="application/rss+xml"/><item><title>Interfaces and Generics: Go's Core Abstraction Mechanisms</title><link>https://blog.mickeyzzc.tech/en/posts/programming/go-interfaces-generics/</link><pubDate>Thu, 12 Feb 2026 10:00:00 +0800</pubDate><guid>https://blog.mickeyzzc.tech/en/posts/programming/go-interfaces-generics/</guid><description>&lt;p&gt;In the previous articles, we covered Go&amp;rsquo;s basic syntax and concurrency model. Now let&amp;rsquo;s dive deep into the two core components of Go&amp;rsquo;s type system—&lt;strong&gt;interfaces&lt;/strong&gt; and &lt;strong&gt;generics&lt;/strong&gt;. These two constitute the foundation of Go&amp;rsquo;s abstraction mechanisms: interfaces provide runtime polymorphism based on behavior, while generics bring compile-time abstraction with type safety.&lt;/p&gt;
&lt;p&gt;Go&amp;rsquo;s design philosophy always emphasizes simplicity. Interfaces adopt &lt;strong&gt;implicit implementation&lt;/strong&gt;, meaning no explicit declaration of implementation relationships is needed. As long as a type possesses the method set required by an interface, it automatically implements that interface. This duck typing style makes code more natural and reduces unnecessary coupling.&lt;/p&gt;</description></item></channel></rss>