3 ms·
Go using casing for access is quick but is awful when you just want to change the access later on. It's not like writing `pub` before the var/field is suddenly
by the_gipsy 4y ago
Go using casing for access is quick but is awful when you just want to change the access later on. It's not like writing `pub` before the var/field is suddenly javaland, see rust.
- aatd86 4y agoWhat do you mean changing the access? You mean from private to public? In that case, you would just have to change a single package. (also, if yes: does it happen often and is that really what we should optimize for then?)
- the_gipsy 4y agoYes, you have to rename a var/field to change public/private. It's not a huge deal of course, just an annoying exception. Re: optimization, what does using casing instead of an explicit `pub` prefix optimize for, exactly? Compiler complexity? Typing ergonomics?
- rawoke083600 4y agoYou ever read the access modifier rules of C++ ? Can you explain that to a newbie in 2 sentences ?
- the_gipsy 4y agoNo, but I don't think that's relevant. Rust or Java access is doesn't require much typing ceremony, and doesn't require you to rename a var to change the access.
- aatd86 4y agoI think it optimizes for readability.