New scope: WeakSingleton

[jasperblues]

This scope will:

• Create a new instance if available
• Allocate it to a pool
• When no classes are using it, drain it from the pool.

[rhgills]

Interesting. This seems like it would just boil down to singleton scope in the case where you are instantiating the entire object graph from a single root object - because, at the time of instantiation, there will always be a class using it.

Are you thinking of using this alongside providers?

[jasperblues]

No, I'm talking about Typhoon having an option to hold weak references to singletons. . . Let's say you have a helper component that's used in some view controllers (but not all). . . On mobile you want this to go away when you're not using it.

[rhgills]

Ahh, right. But to construct the view controller I assume you use a provider, or directly ask the block component factory?

[jasperblues]

Directly asking the factory. . . and weak singleton would make it works as I expect, so I could avoid having to make a provider.

[rhgills]

Gotcha! The pedantic part of me wants to be as decoupled from the DI container as possible, so I'd probably go for the provider. :)

It would be nice if narrow providers could be automatically generated somehow. Off the top of my head, I think Guice does this.

[jasperblues]

Do you have a code-snippet of what that looks like?

[jasperblues]

Closing . . . I put a typo in the title, and its not updating. . . re-opening as a new issue.

[rhgills]

Not sure which issue is the new issue, but to answer your question, without using objective c++ and templates, we'd need to autogenerate some code like:

• (id)newWidget
  {
  return [_factory widget];
  }

along with a setter implementation of the setAssembly: method in < TyphoonInjectionAware >.