[go-nuts] large context and testing

These are two alternatives - you most likely wouldn't want to use those two
together.

Yes.

One recent example (note, code is WIP):
https://github.com/raintreeinc/kbwiki/blob/43d3bc33584da4228fce10fa923341631e71ea25/auth.go#L30

Essentially, I wanted to add separate the OAuth2 + routing logic from the
"Context" (which is intended mainly for setting up all the other services
rather than something by itself.)...

And it's much nicer to say:
sess.LoginURL... rather than sess.Context.LoginURL.


Similarly for your machine case... lets say you have

type Memory interface {
Store(dst uint32, value uint32)
}

type Machine struct {
Memory
}


machine := Machine{simplememory{}}

machine.Store(1, 1241)
vs.
machine.Memory.Store(1, 1241)

Basically, it allows you to compose a bigger thing out of smaller things -
with making it seem like a single thing.

Whether you want it to look as a single thing or not is a different
problem. e.g.

type V2 struct { X, Y int }

type Renderable interface {
RenderAt(V2)
}

type Entity struct {
Pos V2
Vel V2
Renderable
}

func (e *Entity) Render(){ e.RenderAt(e.Pos) }

entity := Entity{V2{0,0}, V2{1,1}, NewTexture("example.png")}
entity.Render()

Basically the main reason I can think of embedding an interfaces is to make
things look as a single cohesive thing without actually making them a
single thing.