Summary

Evaluate and simplify the typed_pool template hierarchy to reduce complexity while maintaining type safety, following Simple Design principle of "Fewest Elements".

Current State

Parallel class hierarchies exist:

Directory: /include/kcenon/thread/impl/typed_pool/ contains 10+ template files

Problem Analysis

• Entire parallel hierarchy for type-safe pooling
• Increases codebase complexity significantly
• May be over-engineered for use cases
• Violates "Fewest Elements" principle

Analysis Tasks

• Document actual usage of typed_pool in dependent projects
• Measure performance difference vs runtime polymorphism
• Evaluate if templates add significant compile-time benefits
• Consider CRTP or policy-based design as alternative

Potential Simplifications

Option A: Keep but document

• If typed_pool provides measurable benefits, document use cases clearly
• Add usage examples in docs/

Option B: Merge with base classes

• Use template specialization on base classes
• Reduce from 2 hierarchies to 1

Option C: Remove typed_pool

• If usage is minimal, deprecate and remove
• Guide users to standard pool with std::any

Acceptance Criteria

• Decision documented with rationale
• If keeping: clear documentation on when to use
• If simplifying: migration path documented
• Code complexity reduced or justified

Notes

This issue requires analysis before implementation. May result in "no change" if typed_pool provides significant value.