learning
/
learn_golang
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
You cannot select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
master
drew/sql-it
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from 'master'
${ noResults }
learn_golang/learn_go_with_tests
History
Drew Bednar 61ddd5d06e Adding additional lines 3 months ago
..
arrays Saving pointers work 8 months ago
concurrency Add debugger nodes and select chapter 4 months ago
dependency_injection Mocking first pass 7 months ago
helloworld Hello world done 11 months ago
integers Integers and example tests 11 months ago
iteration Iteration done 11 months ago
mocking Made sleeper configurable 7 months ago
my_context Adding additional lines 3 months ago
my_maps Finished maps 7 months ago
my_select Add debugger nodes and select chapter 4 months ago
my_sync Finished sync 4 months ago
pointers_errors Mocking first pass 7 months ago
reflection Adding reflection module 4 months ago
structs Saving pointers work 8 months ago
README.md Integers and example tests 11 months ago

README.md
Unescape Escape

Learn Go with Tests

https://quii.gitbook.io/learn-go-with-tests/

Modules and Packages

Go source files can only have one package per directory. This is some "outdated advice" so your mileage may vary. Go 1.22 definitely has more capabilities for packages and how your manage source code. https://dave.cheney.net/2014/12/01/five-suggestions-for-setting-up-a-go-project

  • Name of a package should match the directory name.
  • All lower case, only letters and numbers, NO punctuation.
  • name of a package is part of the name of every public type, const, variable, etc Example: mypkg.MyBuffer. So consider what it looks like to a caller.
  • All files in a package directory must have ethe same package declaration, the exception is test files, _test.go. Test files may declare themselves to be in the same package, but with _test appended to the package declaration. These are known as external tests.
  • packages that are actually commands carry the package main declaration. The name of the command is taken from the name of the packages directory.
  • The go commands; go build, go install, go test, go get, all work with packages, not individual files. go run is the exception to this rule.
  • All packages exist inside a directory tree rooted at $GOPATH/src. Because of this, a package’s import path and a package’s name are often different. The import path is effectively the full path to your package.
  • In Go, the convention is to include the location of the source code in the package’s import path, ie $GOPATH/src/github.com/golang/glog This is not required by the language, it is just a feature of go get.

Testable Examples

https://go.dev/blog/examples

As with typical tests, examples are functions that reside in a package’s _test.go files. Unlike normal test functions, though, example functions take no arguments and begin with the word Example instead of Test.

If your code changes so that the example is no longer valid, your build will fail. Note that the example function will not be executed if you remove the comment // Output: 6. Although the function will be compiled, it won't be executed.

By adding this code the example will appear in the documentation inside godoc, making your code even more accessible.

If you publish your code with examples to a public URL, you can share the documentation of your code at https://pkg.go.dev/