Explore >> Select a destination
|
You are here 
|
www.4async.com | ||
| | | | |
livesys.se
|
|
| | | | | ||
| | | | |
lukesingham.com
|
|
| | | | | These are my summary notes of 'A Tour of Go' - which is meant for people who are familiar with programming to have a quick tour | |
| | | | |
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. | |
| | | | |
ukiahsmith.com
|
|
| | | Go 1.11 introduced a new concept of Modules which brings first class support for managing dependency versions and enabling reproducible builds. Go previously had no notion of dependency versions, and it has been a long and arduous road to get where we are now. Modules do not just copy the style of other programming language's dependency tools, rather it introduces a few slightly different concepts intended to enable programming in the large. | ||
