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.

Sign up for GitHub

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

Jump to bottom

Refactor ResourceManager #151

Open

wateret opened this issue May 6, 2019 · 0 comments

Labels

engine

Owner

wateret commented May 6, 2019 •

edited

Loading

Should let the ResourceManager have two keys.

string id (hold obj as raw pointer)
integer index (hold obj as unique_ptr)

Serialize them in integer index order. (Also ForEach iterates them in integer index order)

Currently we use an integer index for HeroClass but we may use it globally later to enhance performance and memory.

% Should all the classes that are managed by ResourceManager have an integer index member?

The text was updated successfully, but these errors were encountered:

wateret added the engine label

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment