this post was submitted on 13 Jun 2024
23 points (67.2% liked)
Programming
17405 readers
91 users here now
Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!
Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.
Hope you enjoy the instance!
Rules
Rules
- Follow the programming.dev instance rules
- Keep content related to programming in some way
- If you're posting long videos try to add in some form of tldr for those who don't want to watch videos
Wormhole
Follow the wormhole through a path of communities [email protected]
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
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
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.~~ (Edit: Read the reply, I learned something myself. That's why its important that you don't blindly teach people like I did.)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
.