Clipsey ‮✅ is a user on mastodon.social. You can follow them or interact with them if you have an account anywhere in the fediverse. If you don't, you can sign up here.

man idk, Rust is putting up way more of a fight than Golang did for me... I guess that's kind of by design though. octodon.social/media/yjYuGa_nH

Alright I got tic-tac-toe working in both Go and (omg the struggle) Rust!

Here's my long blog post about it: sts10.github.io/2017/11/18/try (tl;dr Rust seems like a really cool idea, but Go seems more practical for most)

Golang repo: github.com/sts10/tic-tac-go

Rust repo: github.com/sts10/rusty-tac

Clipsey ‮✅ @Clipsey

@schlink Here's some nifty golang thing. structs can have attached functions.

So if i make a struct, called vector with 2 inputs of X and Y (int)

type Vector struct {
X int
Y int
}

i can attach a function, like "Add"

func (v *Vector) Add(other Vector) {
return Vector{v.X + other.X, v.Y + other.Y}
}

· Web · 0 · 0

@schlink also, golang can run single-source .go files via the go run (file) command

@Clipsey yep, I used that constantly. Perhaps I should note it in the post...

@schlink oh wait, you already knew, i'm tired with an headache drinking way too much pear cider. Don't mind me.. xD

@Clipsey ah, I feel like that'll be the next thing for me to investigate (that or interfaces).

So this function is named "Add", the input is "other" of type Vector, and... there's no output?

@schlink You need structs before interfaces can be useful, unless you use interface{}, which is golang's form of OOP object class.

@schlink github.com/Member1221/mgj2017 Here's a small game i made in golang for a game jam, tried to make golang be quite OOP with interfaces, feel free to poke around with the code :D

@schlink also, you found a mistake in the code, there should be a return of Vector in the end

@Clipsey ha!

Tell me more about that asterisk though-- `(v *Vector)`. Is that a pointer to your defined type Vector? Why do you need as an asterisk there and I never needed one in my code? What's it called in the docs?

@schlink The asterisk, is indeed a pointer, as i prefer passing around references, also allows you to return nil on errors, and such.

@schlink
func (v *Vector) Add(other Vector) *Vector {
return &Vector{v.X + other.X, v.Y + other.Y}
}

@schlink Fixed version i think idk im too tired

@Clipsey ok, guess I'll have to think of a project where I'll need structs with functions!

@schlink nifty thing with pointers aswell, the inbuilt function new.

pos := new(Vector)
Will return a pointer to vector with default data. (X = 0, Y = 0) as far as i remember.