Interface Pool<TObject>

There are two implementations of Pool:

• SlowPool is useful for development and debugging, as it prevents a few incorrect usage patterns

• FastPoo is intended to be used in the playable builds, it has no internal checks and is faster

  Tips

1. On modern machines memory is usually not a real restriction so for most intents and purposes it's safe to create slightly larger pools than you expec you'll need.
2. Pools require quasi-manual memory management - it's more error prone. Don't just use pools for everything, know when to optimize and only do it when you know you can save some time. An additional read: Optimizing level loading in Trans Neuronica.
3. During development use SlowPool to avoid a certain class of errors from occuring, but when building the game for release go with FastPool.
4. When measuring speed ALWAYS use FastPool, unless you intend to use SlowPool in the final build.
5. The object returned from pool should ideally be stored in as few places as possible, preferably one. This ensures when you need to release the object you won't forget to remove it everywhere.
6. Always release an object back to the pool once you stop using it, otherwise it'll create a nasty memory leak.