https://arran4.github.io/blog/tags/interfaces/Recent content in interfaces on Arrans Technical blogHugo -- gohugo.ioentechnicalblog123@arran4.com (Arran Ubels)technicalblog123@arran4.com (Arran Ubels)Arran Ubels. This work is licensed under a <a rel="license" href="http://creativecommons.org/licenses/by-sa/4.0/">Creative Commons Attribution-ShareAlike 4.0 International License</a>.Wed, 17 Jul 2024 10:17:02 +0000https://arran4.github.io/blog/post/2026/025-compile-time-type-assurance-in-go/Wed, 17 Jul 2024 10:17:02 +0000technicalblog123@arran4.com (Arran Ubels)https://arran4.github.io/blog/post/2026/025-compile-time-type-assurance-in-go/When developing Go applications, we often define interfaces to abstract behavior and decouple components. This promotes testability and clean architecture. However, ensuring that our concrete types actually implement these interfaces can sometimes be a subtle source of errors, especially as codebases evolve. While Go&rsquo;s interface implementation is implicit, meaning you don&rsquo;t explicitly declare that a type implements an interface, it&rsquo;s beneficial to have a mechanism to verify this compliance early on—ideally at compile time.