Flyweight / Mention Singleton

[munificent]

Email from Simon Andersson:

In the flyweight pattern, last section, you mention the need for ensuring only one instance is created.

"To get the advantage of sharing, when you request one, you first see if you’ve already created an identical one. If so, you just return that instance."

Then you mention the factory method pattern. Might the Singleton pattern be mentioned here as well?

[BBauman]

The bullet point underneath mentions using an object pool to handle wrangling and providing created flyweight objects. The pool itself can handle creation of new object types only when none exist, providing the benefits that a Singleton would without requiring the flyweight objects themselves to actually implement the pattern.