Why not use shared_ptr in cocos2dx3?

[justinjia]

I found the v3.0 still uses a customized reference counting mechanism. Why not use shared_ptr? Is there any problem when using shared_ptr?

[TilemapKit]

Came here looking for an answer to the same question. I believe the answer may be in this thread:

Proposal for v3.0: shared_ptr vs. manual retain release

For cocos2d-x v3.0. should we use shared_ptr or manual retain / release ? So, my first was to use shared_ptr, but then I realized that that would imply changing the whole API, so I though that using manual retain/release would be OK (like in v2.1), so I proposed to keep using manual retain/release. If we are going to use manual retain/release, should we still use autorelease, or not ? Let’s see: A) // manual retain/release with autorelease auto action = Sequence::create( MoveBy…

Reading through this and related threads I think it boiled down to CCRef being faster than std::shared_ptr. However, if CC is updated to support multi-threading then shared_ptr was said to be the preferred choice (sometime in the future). Already closed the tabs otherwise I would have added links, sorry.