3 ms·
Further thought: It's probably also necessary to spell out what exactly "equality" means for your operator so that programmers know what they're supposed to be
by tialaramex 5y ago
Further thought: It's probably also necessary to spell out what exactly "equality" means for your operator so that programmers know what they're supposed to be implementing, and what they're getting from other programmers. It's interesting for example that Rust gets away with
assert_eq!(vec![1,2,5,9],[1,2,5,9]);
That's claiming a vector and an array are equal since they have the same integers in them. Neither of Go's notions of equality think these are equal but sure enough they do feel pretty equal in Rust, and in lots of places these would be interchangeable.