


CON: breaking changes with existing pooling techniques.PRO: when using PoolHandles, pooling or non-pooling is completely transparent to the consuming types.add additional install functions to control pooling via installers rather than by explicit code.eliminate all pooling dependancies from the types being pooled.add a PoolHandle struct and IFactory.CreateHandle(), disposing the handle returns object to factory.change pooling to allow a pooled object to be returned to pool via PoolFactory.Free().add Free() to all IFactory types and have the default Free() dispose.move all pooling functionality into the factories.

We look forward to hearing about the cool projects you are building with Zenject and supporting its use!Ĭontact us through github or Upcoming UpdateĪs our Team is looking at Improving and Supporting Zenject, Below is the list of Features and Changes we are planning on applying to Zenject. This is clearly licensed with an MIT license to allow a high degree of flexibility and freedom of use. Modest Tree’s Zenject is open-sourced in order to support the community and encourage collaborative development. To date Zenject has been forked Over 300 times and we love to see the benefit it is deriving for users and support this! We are proud to provide this useful tool to the community and encourage those developing projects to fork from it.
