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

Review options for refactoring asset loading functionality into coroutines. #72

Open
ImmutableOctet opened this issue Apr 27, 2024 · 0 comments
Assignees
Labels
Idea Ideas, concepts, etc. (for features without a clear scope yet) Refactor Used to flag significant codebase refactors

Comments

@ImmutableOctet
Copy link
Owner

ImmutableOctet commented Apr 27, 2024

This has been on my mind for a while, but I only more recently started diving into C++20 coroutines. We could rework our current state-machine-styled Assimp loading functionality into synchronous coroutines via co_await and a scheduler.

@ImmutableOctet ImmutableOctet added Idea Ideas, concepts, etc. (for features without a clear scope yet) Refactor Used to flag significant codebase refactors labels Apr 27, 2024
@ImmutableOctet ImmutableOctet self-assigned this Apr 27, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Idea Ideas, concepts, etc. (for features without a clear scope yet) Refactor Used to flag significant codebase refactors
Projects
None yet
Development

No branches or pull requests

1 participant