/explore

Click through on any links that interest you or select the planets on the right to continue exploring the Outer Web.
You are here

 www.4async.com
Go 1.17
| | www.integralist.co.uk
Go's typed nils are gonna get yer Mark McDonnell
3.3 parsecs away

Travel
| | 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.
| | lukesingham.com
Go Tour Summary
1.7 parsecs away

Travel
| | 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
| | schadokar.dev
Convert Hexadecimal to Decimal and Decimal to Hexadecimal in Golang ยท schadokar.dev
2.8 parsecs away

Travel
| | Convert Hexadecimal to Decimal and Decimal to Hexadecimal
| | parsiya.net
The Golang int and the Overlooked Bug
18.4 parsecs away

Travel
| [AI summary] A post by a security engineer details a subtle bug in Go code where dependence on system architecture (32-bit vs 64-bit) caused an integer overflow during a type conversion, leading to unexpected logic flow and security implications.