-
-
Notifications
You must be signed in to change notification settings - Fork 21.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Convert all references and instances of PoolVector to Vector #36311
Conversation
5a65577
to
2ff87cf
Compare
Since someone asked. Here's the design proposal for converting PoolVector to Vector. https://docs.google.com/document/d/1HtFfENFdnmzB1XhviIqVoeGQbIB1x30vAIFtjTFW18o/edit |
I assume Is there any reason to keep using |
963e1f5
to
fa32513
Compare
Typed `PoolTypeArray` types are now renamed `PackedTypeArray` and are sugar for `Vector<Type>`.
fa32513
to
3205a92
Compare
I rebased to squash the commits and amended to fix build for Mono, Windows and macOS. There are still a few fixes needed for Android, iOS and JavaScript, but since they can't build right now due to the lack of rendering backend, I prefer not to do the changes blindly. |
@aaronfranke no the names are only in the context of Variant and used for exposing API and serialziing. They are called packed because regular arays ini Variant are just arrays of variants. Some contributors used them in their code for unrelated stuff but its not really required. |
Thanks! |
@@ -646,11 +646,6 @@ uint64_t _OS::get_static_memory_peak_usage() const { | |||
return OS::get_singleton()->get_static_memory_peak_usage(); | |||
} | |||
|
|||
uint64_t _OS::get_dynamic_memory_usage() const { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
was this removed by mistake?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I assume no, as the MemoryPool
this referred to was also removed: https://github.com/godotengine/godot/pull/36311/files/3205a92ad872f918c8322cdcd1434c231a1fd251#diff-ab1978b28d0ec282d1df67c7903b6191L419-L422
Should be this section in the docs updated?
https://docs.godotengine.org/en/latest/development/cpp/core_types.html#allocating-memory |
@agar3s Yes. Please make an issue in the docs repo so other contributors can keep track. Or make a PR yourself if you are up to it. :) |
@clayjohn there is an issue already: godotengine/godot-docs#3192 |
No need to lock image anymore. godotengine/godot#36311
Mono: Fix Android build after #36311
Makes no sense to keep PoolVector in a world of 64 bits computers.