https://golang.k5kc.com/tags/interface/Recent content in interface on GolangHugo -- gohugo.ioen-usSun, 16 Aug 2020 00:12:00 +0530https://golang.k5kc.com/2020/08/16/3.inheritance-and-composition/Sun, 16 Aug 2020 00:12:00 +0530https://golang.k5kc.com/2020/08/16/3.inheritance-and-composition/Structs can “inherit” from other structs by a method known as embeding. Here is a simple example: package main import ( "fmt" ) type a struct { Name string } //embeds a value of type a type b struct { a } //embeds a pointer to an a type c struct { *a } func main() { a := a{Name: "Janeway"} fmt.Println(a.Name) b := &b{a: a} fmt.Println(b.Name) c := &c{a: &a} fmt.https://golang.k5kc.com/2020/08/16/2.interface/Sun, 16 Aug 2020 00:11:00 +0530https://golang.k5kc.com/2020/08/16/2.interface/Intro We declare an Interface much like as we define a user defined type. Interfaces decouple different types from each other so we can create more maintainable programs. More: An Interface is a Protocol, a Contract. Bigger the Interface the weaker the abstraction. –> Rob Pike It’s an abstract type. It doesn’t have any implementation. It only describes the expected behavior. The opposite of Abstract Type is Concrete Type. All the types in Go except Interface are of Concrete Type.