Urho have a lot of “bicycle” things.
We cannot just drop things like Urho.Container, but we can stop writing even more garbage code.
So, I suggest to include EASTL as part of 3rdparties available for internal and external usage.
Stop re-re-re-implementing things when some algo or specific container is needed. No more garbage like
Urho::LowerBound-s (shame on me) or maybe even
More functionality for C++devs who dislike STL or want fast containers/compilation.
There shall be the same restriction as for other 3rdparties like Bullet: Urho shall not use EASTL types and things in interface. So, Urho containers will be used for public API and EASTL will be used to simplify some algos or internally store data in exotic containers.