Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Seems to me there are a lot of different types of collections which all have a delete operation. Feels like go forcing you to hand roll a delete forces you to violate the principal that a bit of code should care as little as possible about things it's not about.

If code breaks because list is now a hashmap, that seems like an anti-feature.



> the principal that a bit of code should care as little as possible about things it's not about

Can you find/quote where that principle comes from? I'm genuinely curious.


I think it is mostly based on OOP paradigm, like principle of least knowledge.


It's a motivation for things like OOP, Generics, and macro's.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: