MemoryPool checks if the item it's returning is null or not.

[pnarimani]

Added a simple check to pool to make sure that pool doesn't return or accept null items.

Pull request checklist

Please check if your PR fulfills the following requirements:

• Tests for the changes have been added (for bug fixes / features)
• Docs have been reviewed and added / updated if needed (for bug fixes / features)
• No compiler errors or warnings

Pull request type

Please check the type of change your PR introduces:

• Bugfix
• Feature
• Code style update (formatting, renaming)
• Refactoring (no functional changes, no api changes)
• Build related changes
• Documentation content changes
• Other (please describe):

What is the current behavior?

1. You return an object to pool
2. Destroy the object
3. Pool doesn't check if the object is destroyed and will return the null object in Spawn method.

What is the new behavior?

Pool will check if the item that is about to be returned is null or not.

Does this introduce a breaking change?

• Yes
• No

On which Unity version has this been tested?

• 2021 LTS

Scripting backend:

• Mono
• IL2CPP

[Mathijs-Bakker]

I see! Good comment. And solution.