32 lines
1.9 KiB
Plaintext
32 lines
1.9 KiB
Plaintext
* long term feature: shared_ptr less locator and resource cache
|
|
* debugging tools (#60): the issue online already contains interesting tips on this, look at it
|
|
* work stealing job system (see #100) + mt scheduler based on const awareness for types
|
|
* allow to replace std:: with custom implementations
|
|
* add examples (and credits) from @alanjfs :)
|
|
* custom pools example (multi instance, tables, enable/disable, and so on...)
|
|
|
|
WIP:
|
|
* custom allocators all over
|
|
|
|
WIP:
|
|
* make pools available (registry/view/group), review operator| for views
|
|
* compressed pair to exploit ebo in sparse set and the others
|
|
* isolate view iterator, unwrap iterators in registry ::remove/::erase/::destroy to use the faster solution for non-view iterators
|
|
* meta: use forward_as_any to forward arguments from eg meta_func::invoke, so as to remove the need for the user to explicitly forward references
|
|
* scheduler, use any (or poly?) instead of unique_ptr
|
|
* resource, forward the id to the loader from the cache and if constexpr the call to load, update doc and describe customization points
|
|
* make it possible to create views of the type `view<T, T>`, add get by index and such, allow to register custom pools by name with the registry
|
|
* add user data to type_info
|
|
* any_vector for context variables
|
|
* make const registry::view thread safe, switch to a view<T...>{registry} model (long term goal)
|
|
* weak reference wrapper example with custom storage
|
|
* headless (sparse set only) view
|
|
* write documentation for custom storages and views!!
|
|
* registry: use a poly object for pools, no more pool_data type.
|
|
* make runtime views use opaque storage and therefore return also elements.
|
|
* add exclude-only views to combine with packs
|
|
* entity-aware observer, add observer functions aside observer class
|
|
* deprecate non-owning groups in favor of owning views and view packs, introduce lazy owning views
|
|
* snapshot: support for range-based archives
|
|
* add example: 64 bit ids with 32 bits reserved for users' purposes
|