this post was submitted on 13 Jun 2024
24 points (67.6% liked)

Programming

17433 readers
237 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 !webdev@programming.dev

founded 1 year ago
MODERATORS
snowe@programming.dev
Ategon@programming.dev
MaungaHikoi@lemmy.nz
24
Why is Go syntax so messy (lemmy.ca)
submitted 5 months ago by urska@lemmy.ca to c/programming@programming.dev
21 comments fedilink hide all child comments
 

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 viewing a single comment's thread
view the rest of the comments
[โ€“] Vivendi@lemmy.zip 3 points 5 months ago (1 children)

It goes back to mathematics pseudo code which was then used to sketch the ALGOL symbols way back in the days and which then gave birth to everything you know of programming today

That shit's quite ancient

[โ€“] thingsiplay@beehaw.org 0 points 5 months ago* (last edited 5 months ago)

~~But that mathematical pseudo code has nothing in common with the walrus operator := in Python and Go. They are just the same symbols, but with a totally different meaning and use case. Its an operator designed specifically for programming languages, because that is not applicable to mathematics at all. In mathematics you don't have an assignment operator a = 69 that cannot be used as part of an expression. Therefore you don't need a dedicated := that yields an expression that can be used as part of an expression and create a variable if its not already.~~ (Edit: I'm so sick of my stupidness.)