How to name a function in Go, CamelCase or Semi-CamelCase?

Question

I want to write a function in Go to insert a document into a collection in a MongoDB database. Which way to name the function is better,
writeToMongoDB or
WriteToMongoD?

The second is CamelCase, while I saw someone using the style of the first one, so I am not sure which one is more appropriate. Thanks.

Gopher · Accepted Answer

Syntax In Go this is not a matter of style, it is a matter of syntax. Exported names (that is, identifiers that can be used from a package other than the one where they are defined) begin with a capital letter. Thus if your method is part of your public API, it should be written: WriteToDB but if it is an internal helper method it should be written: writeToDB The benefit of doing it this way over using keywords to define exportedness (extern, public, etc.) is that making it a part of the name ensures that anywhere an identifier is used you can tell if it is exported or not without having to find where it was defined (to see if the definition contains a keyword). See also: Exported Identifiers from the spec. i18n Because Go is UTF-8 encoded and supports any Unicode character with the letters or numers property in identifier names some people in locales that don't have a concept of case may have trouble creating exported methods (the default is non-exported). In this case (pun intended) it is common to prefix identifiers with an X to indicate exportedness. For example: X日本語 See also: What's up with Unicode identifiers? from the FAQ. In Go, it is convention to uses mixed cap. From the docs:https://golang.org/doc/effective_go.html#mixed-caps

Go Language

Similar Questions

Golang if/else not compiling, function ends without a return statement.

How to Pass variable in URL golang?

How to serve a static html file using a go web server?

On a mission to build Next-Gen Community Platform for Developers

Facebook

Twitter

Linkedin

Instagram