4 ms·

Yes, Type safe. You can not interpret something as a different kind of type via the use of interface{}. Contrast that with void-pointers, which make that so eas

Yes, Type safe. You can not interpret something as a different kind of type via the use of interface{}. Contrast that with void-pointers, which make that so easy as to be a common bug-source. It's not statically type-checked, yes. That's fine too, in my opinion, but also irrelevant for a comparison with void-pointers (because they also don't provide that). In summary, interface{} is strictly better than void-pointers. Which was exactly my point. Equating the two is intellectually dishonest.

saghm 9y ago
> Yes, Type safe. You can not interpret something as a different kind of type via the use of interface{}. Interesting; for some reason, I was under the impression that you could cast an `interface{}` arbitrarily, but from trying it out, you're absolutely correct. (I should definitely make sure to try these things out before confidently asserting about them...) > interface{} is strictly better than void-pointers No arguments here; even if for some reason they weren't type safe (which they are, much to my surprise), I'd still agree with you there.