When you see .unwrap in Rust code, you know it smells bad.
When you see x, _ := in Go code, you know it smells bad.
> But if you don't know Go, it's just an underscore.
And if you don't know rust, .unwrap is just a getter method.
> But if you don't know Go, it's just an underscore.
And if you don't know rust, .unwrap is just a getter method.
But I'm just explaining the argument as I understand it to the commenter who asked. I'm not saying it is right. They have tradeoffs and perhaps you prefer Go's tradeoffs.
What if it’s a function that returns the coordinates of a vector and you don’t care about the y coordinate?
x, _ :=
func ParseStringToBase10i32AndIDoNotCare(s string) {
i, _ := strconv.ParseInt(s, 10, 32)
return i
}
Ignoring an output data value or set is just fine. Don't always need the key and value of a map. Nor a y axes in vector<x,y,z> math.