Skip to content
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

Refactor ecs::details::component_info #78

Merged
merged 6 commits into from
Dec 10, 2022

Conversation

JessyDL
Copy link
Owner

@JessyDL JessyDL commented Dec 5, 2022

This PR implements #64

  • component_info is now component_container_t
  • The component_info_typed variations now point to the specialized _untyped and _flag implementations.
  • Added draft component_info that partially defaults to type agnostic memory for eligible types.
  • Fixed defaults for staged_sparse_memory_region_t
  • Temporarily added a conversion method to transform stages into the enum value. see deprecate numbered component stage ranges #79
  • Forcibly inlined staged_sparse_memory_region_t to remove performance discrepency with ecs::details::staged_sparse_array_t it is meant to replace. As it is only used in component_info, and as it is a detail implementation of the ECS, it should not be leaking and causing binary bloat.

It should now be possible for types that satisfy component_type::TRIVIAL and component_type::FLAG to implement serialization safely.

…emory.

Fixed defaults for `staged_sparse_memory_region_t`
Temporarily added a conversion method to transform stages into the enum value
@JessyDL JessyDL added the feature label Dec 5, 2022
@JessyDL JessyDL added this to the 0.2.0 milestone Dec 5, 2022
@JessyDL JessyDL self-assigned this Dec 5, 2022
@JessyDL JessyDL marked this pull request as ready for review December 5, 2022 23:00
renamed `component_info` to `component_container_t`
purged irrelevant implementations of `component_info`
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant