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

Implement hash-based lookup and creation for archetypes #75

Open
ImmutableOctet opened this issue Jul 15, 2024 · 0 comments
Open

Implement hash-based lookup and creation for archetypes #75

ImmutableOctet opened this issue Jul 15, 2024 · 0 comments
Assignees
Labels
Good practice Indicates a proposed change that would be seen as good practice module: engine For features that involve the `engine` module. (optional) Refactor Used to flag significant codebase refactors

Comments

@ImmutableOctet
Copy link
Owner

Archetypes are currently mapped using standard containers, where the file path is stored as the key to the processed entity descriptor. We should change the key to only be a hash of the archetype path, or have a separate mechanism for finding entries based on the string hash.

The creation mechanism mentioned in #74 would be made more efficient with this change as we wouldn't need to store a string for every creation request.

@ImmutableOctet ImmutableOctet added Good practice Indicates a proposed change that would be seen as good practice module: engine For features that involve the `engine` module. (optional) Refactor Used to flag significant codebase refactors labels Jul 15, 2024
@ImmutableOctet ImmutableOctet self-assigned this Jul 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Good practice Indicates a proposed change that would be seen as good practice module: engine For features that involve the `engine` module. (optional) Refactor Used to flag significant codebase refactors
Projects
None yet
Development

No branches or pull requests

1 participant