This repository has been archived by the owner on Jan 5, 2023. It is now read-only.
[Do not integrate] Enforce LIFO callbacks #8
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
- maintaining the order of return instead of complaining (Callbacks execute in a single process and preempt themselves to avoid returning) - TFSameThreadRunner is made a singleton to have a single callback executor
This is safe to do now that TFSameThreadProcess is a singleton
- support for ffiCall:module: - default runner is same thread runner
guillep
changed the title
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Instead of just forbidding callbacks to return, enforce that callbacks do return in LIFO order