znkr@chandlerc, re https://chandlerc.blog/posts/little_things_1_access/. What I like about Go‘s way of defining public functions is that it’s easy to understand the access level at the call site. I never new I wanted that until I started reading code in another language after reading a lot of Go code. The other thing I like is that changing the access level highlights all usages during code review.
The little things #1: Access control
This post is part of a series looking at little details of programming language design, mostly in the context of Carbon. Check out the series intro post for context and other entries. Let’s talk about public vs. private! Folks who know C++ may be familiar with these concepts, but here is a quick example: class MyType { public: void MyPublicFunction(); private: void InternalDetail(); }; One of the things that has always been frustrating to me are exactly how public and private work here.
Chandler Carruth