Programming

17651 readers

454 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

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 2 years ago

MODERATORS

[email protected]

Why is Go syntax so messy (lemmy.ca)

submitted 6 months ago by [email protected] to c/[email protected]

13 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

[–] [email protected] -1 points 6 months ago

I'm not triggered by any of this. I'm not sure why my thinking the question is inane would count as "being triggered".

Upvotes does not necessarily mean people agree with OP’s stance.

It should mean they think it's a useful/interesting question and I think it very much is not. It's just someone whining that it doesn't look like something they're used to and a bunch of very patient people generously leading them through the very basics of the language that's well covered in many introductory tutorials - as such it makes it all a waste of time and worthy of being buried.