We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
To achieve hot reload, user's code should be shared library(or wasm), which we can load/unload during execution.
For example,
So, runtime keep memory state even on reload user code. we can refresh small amount of component which the type of state or props changed.
What we need to research is
The text was updated successfully, but these errors were encountered:
prototype example https://github.com/namse/rust-plugin-example
using function pointer setting.
extern "Rust" with dylib seems not working. So I decided to use function pointer setting.
Sorry, something went wrong.
I think hot reload is very dangerous depending on what kind of state user will save in hooks system.
Some topics we have to research,
No branches or pull requests
To achieve hot reload, user's code should be shared library(or wasm), which we can load/unload during execution.
For example,
So, runtime keep memory state even on reload user code. we can refresh small amount of component which the type of state or props changed.
What we need to research is
The text was updated successfully, but these errors were encountered: