design/

Sample program demonstrating when implicit interface conversions are provided by the compiler.

Sample program demonstrating that type assertions are a runtime and not compile time construct.

Sample program to show how method sets can affect behavior.

Sample program demonstrating struct composition.

Sample program demonstrating decoupling with interfaces.

Sample program demonstrating interface composition.

Sample program demonstrating decoupling with interface composition.

Sample program demonstrating removing interface pollution.

Sample program demonstrating being more precise with API design.

Using the template, declare a set of concrete types that implement the set of predefined interface types.

This is an example of using type hierarchies with a OOP pattern.

This is an example of using composition and interfaces.

Sample program to show how you can personally mock concrete types when you need to for your own packages or tests.

Package pubsub simulates a package that provides publication/subscription type services.

This is an example that creates interface pollution by improperly using an interface when one is not needed.

This is an example that removes the interface pollution by removing the interface and using the concrete type directly.

Sample program to show how the default error type is implemented.

Sample program to show how to use error variables to help the caller determine the exact error being returned.

http://golang.org/src/pkg/encoding/json/decode.go Sample program to show how to implement a custom error type based on the json package in the standard library.

Package example5 provides code to show how to implement behavior as context.

Sample program to show see if the class can find the bug.

Sample program to show see if the class can find the bug.

Sample program to show how wrapping errors work.

Create two error variables, one called ErrInvalidValue and the other called ErrAmountTooLarge.

Create a custom error type called appError that contains three fields, err error, message string and code int.

Create two error variables, one called ErrInvalidValue and the other called ErrAmountTooLarge.

Create a custom error type called appError that contains three fields, err error, message string and code int.