Go Gab

Today we talk about whether Go is a pass-by-reference or pass-by-value language.

I wanted to talk briefly about methods vs functions as a way of laying the groundwork for future topics such as pointers and references. This episode answers the question, "What is the difference between a method and a function?". References Practical Object Oriented Design in Ruby (http://www.poodr.com/)

Three minutes isn't nearly long enough to talk about the rune data type in Go, but I tried anyway. Here are some good resources related to character encoding and memory allocation: The Absolute Minimum Every Software Developer Absolutely, Positively Must Know About Unicode and Character Sets (No Excuses!) by Joel Spolsky (http://www.joelonsoftware.com/articles/Unicode.html) Strings, bytes, runes and characters in Go (http://blog.golang.org/strings) Rune literals in the Go spec (https://golang.org/ref/spec#Rune_literals) Things I didn't cover: * Why does byte alias an unsigned integer (uint8), but rune aliases a signed integer (int32)? Turns out if you ask that in the Go Google Group, they get a bit annoyed (https://groups.google.com/forum/#!topic/golang-nuts/d3_GPK8bwBg). Edit At about 2:10, I say, "When it gets more complicated is when you need to represent multi-characters [sic]." I misspoke, and meant to say multibyte characters.

Coming to terms with Go's concurrency model, investigating how the main function operates.

An introduction to Go Gab.