internal/goose/testdata/InterfaceBindingReuse/foo/foo_goose.go

//+build gooseinject

package main

import (
	"codename/goose"
)

func injectFooBar() FooBar {
	panic(goose.Use(
		provideBar,
		provideFooBar,
		goose.Bind(Fooer(nil), (*Bar)(nil))))
}
goose: add interface binding An interface binding instructs goose that a concrete type should be used to satisfy a dependency on an interface type. goose could determine this implicitly, but having an explicit directive makes the provider author's intent clear and allows different concrete types to satisfy different smaller interfaces. Reviewed-by: Tuo Shan <shantuo@google.com> 2018-04-02 14:08:17 -07:00			`//+build gooseinject`

			`package main`

goose: use marker functions instead of comments To avoid making this CL too large, I did not migrate the existing goose comments through the repository. This will be addressed in a subsequent CL. Reviewed-by: Tuo Shan <shantuo@google.com> 2018-04-27 13:44:54 -04:00			`import (`
			`"codename/goose"`
			`)`
goose: add interface binding An interface binding instructs goose that a concrete type should be used to satisfy a dependency on an interface type. goose could determine this implicitly, but having an explicit directive makes the provider author's intent clear and allows different concrete types to satisfy different smaller interfaces. Reviewed-by: Tuo Shan <shantuo@google.com> 2018-04-02 14:08:17 -07:00
goose: use marker functions instead of comments To avoid making this CL too large, I did not migrate the existing goose comments through the repository. This will be addressed in a subsequent CL. Reviewed-by: Tuo Shan <shantuo@google.com> 2018-04-27 13:44:54 -04:00			`func injectFooBar() FooBar {`
			`panic(goose.Use(`
			`provideBar,`
			`provideFooBar,`
			`goose.Bind(Fooer(nil), (*Bar)(nil))))`
			`}`