Programming

17430 readers

75 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 1 year ago

MODERATORS

snowe

Ategon

[email protected]

Why is Go syntax so messy (lemmy.ca)

submitted 5 months ago by [email protected] to c/programming

23 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] 15 points 5 months ago* (last edited 5 months ago)

but Im seeing syntax that Ive never seen in my life

Which languages do you know? What is your background?

What is wrong with "var test int"? There is no need for a return type, if the function returns nothing. Thats the language design and I think it is easy to remember.

func(u User) hi ()

u is something like self in Python and hi() is a method of User.

Please explain why do you think something is too messy, also with which languages you have already worked.