功能的命名约定

Question

In documentation, they use camel case and pascal case both. Is this convention different for functions and methods? Does it decide scope of a function ?

Answer 1

Yes. In Go a field/method is exported if it begins with an upper cased letter while it is unexported if the first letter of the identifier is lower cased. This is similar to the public/private features in most OO languages. Here's an example or two;

package "a"

func ThisFunctionIsExported() {}

func thisOneIsNot() {}


...

package "b"

import "a"

a.ThisFunctionIsExported() // works

a.thisOneIsNot() // compiler error

So, yes the developer is consciously deciding what the scope of those methods are with their casing choice. Lower cased functions are always helper methods inside the package scope, they aren't exposed in importing scopes.