-
Notifications
You must be signed in to change notification settings - Fork 27
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
Does the call stack need to be empty for the later code to be run? #159
Comments
Callbacks in the event loop can be run in these two ways:
So you can run the event loop at any time by calling |
Thank you for the quick response. Could you maybe go into more detail why the call stack needs to be empty? Is this a technical limitation or a design decision by Edit: It seems like Rhttpd.c does not check the call stack. Would it be possible to add a |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I use later in my package to call R from a C++ background thread in a safe way.
From looking in the source code I assume
later
waits for some regular callbacks and, if the call stack is empty thelater
code is run.(Please correct me if these assumptions are wrong)
Does the call stack need to be completely empty for technical reasons or could
later
run code while R is in a loop or executing other code?For example: I would like to execute code while R waits for keyboard inputs:
Expected output:
(Text is printed 1 sec after execution, before enter is pressed)
Actual output:
(Text is printed after enter is pressed)
Possibly similar issue: #152
The text was updated successfully, but these errors were encountered: