Golang

golang@programming.dev

2,737 readers

82 active

1 user here now

This is a community dedicated to the go programming language.

Useful Links:

Rules:

Posts must be relevant to Go
No NSFW content
No hate speech, bigotry, etc
Try to keep discussions on topic
No spam of tools/companies/advertisements
It’s OK to post your own stuff part of the time, but the primary use of the community should not be self-promotion.

founded 3 years ago

moderators

Ategon@programming.dev

austin@programming.dev

RandomDevOpsDude@programming.dev

Fighting Rust Anxiety: Insights from a Go Developer, Navigating Rust Syntax Shenanigans (arriqaaq.substack.com)

submitted 3 years ago by nebiros@programming.dev to c/golang@programming.dev

15 comments fedilink hide all child comments

you are viewing a single comment's thread
view the rest of the comments

[–] wilk@masto.bike 0 points 3 years ago (2 children)

@gnus_migrate @nebiros In Go we consider errors as values and not fatal or exceptions. For example sql.ErrNoRows , io.EOF, custom... It's why they are returned and used like any other values.

permalink

fedilink

source

parent

hideshow 4 child comments

[–] zygo_histo_morpheus@programming.dev 2 points 3 years ago

Errors are values in rust too. There are a couple of differences, like the ? syntax, rust returning a value or an error instead of a value and an error (or nil) for example, but everything you wrote applies to rust as well.

permalink

fedilink

source

parent

[–] gnus_migrate@programming.dev 2 points 3 years ago

The difference is that you can't have a generic mechanism in Go for error handling. It's basically up to the programmer, and every if error != nil line is a potential source of bugs.

permalink

fedilink

source

parent

lemmy:	0.19.20
mlmym (mschae):	26.3.4