Add a persistent state table that uses a destructor upon reloads #5
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There is a need for semi-persistence in some cases. Especially threads may make use
of this functionality: the thread needs to be reloaded but its previous instance must
be killed. For this we need to persist the variable until after the reload and then
kill the thread
An example:
On my webserver I have a thread that performs certain IO operations periodically, however,
I want it to be reloaded (and the old instance killed) whenever I change a file. This would
be a very good addition to the library.