Explore >> Select a destination
|
You are here 
|
blog.nuculabs.de | ||
| | | | |
www.4async.com
|
|
| | | | | ???Go?1.17???????????????????????1.17????????????????????????1.18????????????????6?????????????????????Go 1.18??????????1.17??????????????? ???????? ???Go????????????????????????????????????interface{}????????????????????????????????????????????????????????????????????Go??????????????????????????????????????????????????????interface{}????????????????????????????????????????????????????????????????????????????????????????????? ?Go????????????????????????????????????????????????????????????????????????????... | |
| | | | |
www.integralist.co.uk
|
|
| | | | | The following code doesn't do what you might expect: package main import "fmt" func main() { var i *impl fmt.Println("i == nil:", i == nil) what(i) } type impl struct{} func (i *impl) do() {} func what(i interface{ do() }) { fmt.Println("i == nil:", i == nil) } If you expected the what function to print i == nil: true, then keep reading... Typed Nils The behavior observed is due to the way interfaces and nil values interact in Go. | |
| | | | |
infinitedigits.co
|
|
| | | | | Exploring meta-behaviors. | |
| | | | |
alexrichey.com
|
|
| | | A pattern for distinguishing and handling client and internal errors in Go that leverages the power of Go's interfaces. | ||
