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.

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

Implement a proof of concept for code hotswapping #95

Open
Duttenheim opened this issue Aug 18, 2022 · 0 comments
Open

Implement a proof of concept for code hotswapping #95

Duttenheim opened this issue Aug 18, 2022 · 0 comments
Labels
category: build Building with CMake, pre/post build hooks category: experiment Experiments category: foundation Containers, math, network implementation, threading and synchronisation, etc feature request New features we should implement

Comments

@Duttenheim
Copy link
Contributor

Since we build the engine in a heavily data-oriented way, the way our jobs run is very straight-forward, no lambdas with closures, everything is a pointer to memory etc, it should be possible to put a thread job in a dynamic library and replace it at runtime whenever changes occur.
@Duttenheim Duttenheim added category: foundation Containers, math, network implementation, threading and synchronisation, etc feature request New features we should implement category: experiment Experiments category: build Building with CMake, pre/post build hooks labels Aug 18, 2022
@Duttenheim Duttenheim changed the title Implement a proof of concept for code hotswapping. Implement a proof of concept for code hotswapping Aug 18, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
category: build Building with CMake, pre/post build hooks category: experiment Experiments category: foundation Containers, math, network implementation, threading and synchronisation, etc feature request New features we should implement
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@Duttenheim