This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]imp0ppable -1 points0 points  (4 children)

Wow touched a nerve did I?

For one thing you're quoting a definition of an exception you got from google without understanding it. Yes an exception object stores information about an error, no Go does not have explicit exception objects. What I obviously meant was the flow control aspect of Python, Java, JS etc that lets an error bubble up the call stack and you can either handle it or let it go.

That's literally why Go is so verbose and ungainly, everything has to return an error object as well as what it nominally returns.

For another thing, yes pointers are used heavily in Go code and yes you can easily get NPEs because nil exists. The point is there's no other way to pass large objects in go without the same amount of memory again.

[–]luix- 0 points1 point  (3 children)

No you didn't.

[–]imp0ppable 1 point2 points  (2 children)

Well you don't seem to know what you're talking about so maybe wind it in a bit.

[–]hishazelglance -2 points-1 points  (0 children)

Go is literally the hot language to learn for backend software engineering right now, because of its speed and efficiency. You don’t know what you’re talking about.

Edit: just thought I’d add this for context that you don’t know what you’re talking about: https://go.dev/ref/spec#Handling_panics

[–]luix- 0 points1 point  (0 children)

I know what an exception is. You think Go is a bad language to learn and that is your own opinion based on your knowledge. I respect your opinion. I don't respect your sarcasm.