Learn Go: Hand-crafted Go exercises and examples

Post by grey-area » Sun, May 17, 2020, 5:43 AM UTC

loudlambda wrote: post #24

edem wrote: post #12

This doesn't ask the most important question: why would I learn Go at all?

To answer the question: what would a language look like if you put it's designers in a time capsule for 20+ years and had them make a language that was uninformed by all the language advances and learnings they'd missed out on.

Post by littlestymaar » Sun, May 17, 2020, 6:25 AM UTC

slimsag wrote: post #21

littlestymaar wrote: post #13

Earlier quoted context omitted.

I learned Rust & Go pretty much at the same time, and it actually works quite well because most of the paradigms are actually the same (structs & function implementation on top of them, error as return value). Rust is clearer about the point you mention[1], while Go introduction spend more time explaining things like threads and channels (which I wasn't familiar with), and finally Rust help you to use them properly,…

Yeah, Go focusing on threads and channels I agree is generally a painful new concept for beginners to learn. I've also seen beginners often "over-correct" and start using channels and goroutines for things they really shouldn't. How was your learning experience with Rust's borrow checking and pointers? Was it introduced to you early on, or later on?

Post by triztian » Sun, May 17, 2020, 7:06 AM UTC

efiecho wrote: post #44

I have not yet been able to find a simple "Hello World" example of starting a new project with Go modules instead of $GOPATH.

    #!/bin/bash

    cd $HOME

    # Create project directory
    mkdir hellogo

    cd hellogo

    # Init project modfile
    go mod init example.com/hellogo

    # Create the main source file
    # Uses bash's heredoc
    cat  ./main.go
    package main
    import "fmt"
    func main() {
        fmt.Print("Hello world")
    }
    EOF

    # Build it
    go build

    # Run it
    ./hellogo

Post by DabbyDabberson » Sun, May 17, 2020, 8:53 AM UTC

SomaticPirate wrote: post #25

slimsag wrote: post #7

Earlier quoted context omitted.

That's definitely true, but I've often seen beginners just say: type Foo struct { ... } func (f *Foo) Bar() { ... } And go "Aha, that's an object and a method, I get it!" but when asked whether they should be using a pointer there or not, have no idea what that even entails. In other words, it's possible to neglect the details of pointers easily and have things generally work

William Kennedy has an excellent post on this https://www.ardanlabs.com/blog/2017/06/design-philosophy-on-... As someone who has written (and read) a decent amount of Go the value vs pointer semantics of the function informs me of how the creator intends for the type to be used. Seeing pointer receivers informs me that there is an expectation of modifying the state while value pointers (which are thankfully more comm…

Post by sk0g » Sun, May 17, 2020, 9:16 AM UTC

triztian wrote: post #45

efiecho wrote: post #44

I have not yet been able to find a simple "Hello World" example of starting a new project with Go modules instead of $GOPATH.

Hey there I found modules to be confusing coming from GOPATH too, but they're straight forward, super barebones example: #!/bin/bash cd $HOME # Create project directory mkdir hellogo cd hellogo # Init project modfile go mod init example.com/hellogo # Create the main source file # Uses bash's heredoc cat ./main.go package main import "fmt" func main() { fmt.Print("Hello world") } EOF # Build it go build # Run it ./hel…