: public? : too long : pub? : too long *takes huge bong rip* : capitalise the first letter of the variable name? : shipit!
-
-
Oh my god, yes, that is so annoying
-
It’s one of so many Go decisions that seems clever at first glance, but doesn’t work in practice—then the language team dug in their heels as always and refused to change it. :(
- 3 more replies
New conversation -
-
-
this isn't a big deal, because all your files are in the same Google monorepo :)
-
Just because a problem can be made less annoying doesn’t change the fact that it’s still a problem that exists for no reason other than aesthetic preferences of Rob Pike
- 1 more reply
New conversation -
-
-
With modern editors, changing symbol names is as difficult as <right-click> -> change symbol. I'll take that non-existent inconvenience for at-a-glance recognition of exported symbols wherever I might find them.
-
The vast majority of the time I don’t really care whether a symbol is public or private when I’m *using* it. Only at declaration does it really matter. And it is obviously a pain point for a lot of people.
- 2 more replies
New conversation -
-
-
Sounds like you think writing code is more important than reading it.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
Then the compiler does not need visibility checks, it is all in the syntax! *genius* \s
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
well, there's a tool for that!
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.