If I implement that, the code will work just fine, but I feel like I'd have broken some golden NO-OBJECTS rule of entity design. I've implemented animations in other fashions but they don't have quite the capability --- I've not been able to put multiple animations on a single altas, or have animations where the frame width and height could change.
I don't understand why you can't have a resizable container and objects inside a component.
Containers and objects are good way to encapsulate and store data.
Raw data doesn't mean that you only can have primitive types in a component. What you want to stay away from is having lots of functions in a component. That's system's job.
I am a noob here. So I have a noobish question. I just received a downvote for this post. Is there a reason for this, and something I can avoid in the future? Because I don't like offending people or posting inappropriate content.
+1 to compensate for that downvote. It is an obvious fact that new is slow, so someone could've thought your question was ridiculous especially when you caught attention of people by capitalizing SLOW!
What's the big o notation for push() and pop() in priority_queue with vector or deque as its underlying container.
I can't find this anywhere.
I'm guessing linear complexity at worst for push() because it has to search for right place to insert.