Replies: 1 comment
-
|
Lis decouples casing and visibility precisely because it shares your concern. But rewriting foreign identifiers is a step too far, because of loss of familiarity (uncanniness) and muscle memory for Go users, departure from official spelling in stdlib and third-party libs throughout the Go ecosystem, lossy mapping (e.g. initialisms), lack of uniformity as Lis types are PascalCased themselves, codegen and name resolution complexity, etc. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
What I don't like about Go is that it abuses the case of the first letter for visibility: if I want to change the visibility of some function/variable/struct, I want to do that an one place, not everywhere where it already is used.
Currently, it requires to use Upper case for accessing public Go elements, e.g.
fmt.Printlnorstrings.Buffer. Could it be changed that way, that one could writefmt.printlnand the compiler will that transpile tofmt.Printlnbecause it knows it must be public?Beta Was this translation helpful? Give feedback.
All reactions