4 ms·
> When you see x, _ := in Go code, you know it smells bad. What if it’s a function that returns the coordinates of a vector and you don’t care about the y coor
by xigoi 8mo ago
> When you see x, _ := in Go code, you know it smells bad.
What if it’s a function that returns the coordinates of a vector and you don’t care about the y coordinate?
- yndoendo 8mo agoHaven't jumped into rust for a while. Had to read up on what .unwrap() does. x, _ := With the topic of .unwrap() _ is referencing an ignored error. Better laid out as: func ParseStringToBase10i32AndIDoNotCare(s string) { i, _ := strconv.ParseInt(s, 10, 32) return i } Un-handled errors in Go keeps the application going were rust crashes .unwrap(). 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.