I'd love to see people using and contributing to this library! To keep it easier for people down the line, you must follow these rules about code formatting so that people can have the opportunity to enjoy working with and contributing this library.
- Code must be
go fmt
-ed - Code must pass
go lint
- Code must pass
go vet
- Code must be organized in a manner coherent with the rest of the package
- You must have tests! Pretty comprehensive ones.
- You must document/comment your code well
- Any
golang
standards not mentioned here apply as well (use of interfaces, etc.)