I understand Rust being type safe, but Im seeing syntax that Ive never seen in my life in Go which looks too messy
var test int < bruh what?
:=
func(u User) hi () { … } Where is the return type and why calling this fct doesnt require passing the u parameter but rather u.hi().
map := map[string] int {} < wtf
You are probably right about that. But don’t forget that the operator didn’t made it day one, there was lot of discussion before and probably testing it in the beta releases before. But given how old Golang at that point is, you are right about my take on inspiration. This operator wasn’t a new invention in Python.
Does it though? In both cases, Go and Python, the operator will assign a variable a value and also use it as an expression. That is useful in cases like for loops or other cases where you want immediately use the variable content as an expression. This cannot be done with the regular assignment operator(Edit: Read the reply, I learned something myself. That’s why its important that you don’t blindly teach people like I did.)a = 69
, which itself is not an expression. So in practical terms, its the same in usability for Go and Python. So its doing the same for both languages and has the same differences to the assignment operator.That is absolutely not true.
foo := <expr>
is a statement in Go, full stop. Just try something trivial like assigning to the output of:=
: https://go.dev/play/p/nPINGc7LO8BIt’s true that
if
andfor
let you use:=
but don’t let you usevar
, but you still can’t use the result of the assignment directly. So for instance you needif foo := <expr>; foo { ... }
rather than justif foo := <expr> { ... }
.Ok I see, I stand corrected then. Its a misconception I had without actually going through all of this, so my bad (will edit my replies to mark them). At least in Python we can do this
print(foo := (bar := 3))
but not on its own asfoo := 3
.