this post was submitted on 26 Jan 2024
35 points (94.9% liked)
Rust
6013 readers
3 users here now
Welcome to the Rust community! This is a place to discuss about the Rust programming language.
Wormhole
Credits
- The icon is a modified version of the official rust logo (changing the colors to a gradient and black background)
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
The best solution here is a map, using keys as the set. So something like:
I haven't used Go's new generics, but I'm guessing this would work fine, provided
T
is a value type (or can be converted to one). If you know you need deduplication at the start, just use amap
at the start.If you don't have value types, you're going to have a hard time regardless of language (would probably need some OOP features, which adds a ton of complexity). But you can get pretty far with that pattern. If you add a
Hash() int
to your type:That's what error wrapping is for:
This makes it so you can use the
errors
package to unwrap errors or check if an error is a given type. Or you can propagate it like I've shown above.So I see this as programmer error. Rust has the same issue since it's easy to just throw a
?
in there and bail early without additional context. The simpler form is easier to catch in Go vs Rust in a code review because it's more verbose.It seems you don't like verbosity, which is fair. I'm fine with verbosity, I don't like surprises, and Go has enough of those that I generally avoid it.