-
Notifications
You must be signed in to change notification settings - Fork 6
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
Synchroneous task #44
Comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Synchronous tasks
In the originating work on Real Time for the Masses, tasks could also be run synchronously, i.e., one could call into other tasks as a function call, this allowed to re-factor code along the following lines (not actual syntax)
The static analysis could figure out that
X
was (synchronously) accessed by tasksa
andb
. The resource usage was local toc
, so you did not need to declare it as a resource of botha
andb
.Also as full program analysis was done you did not need to declare the use of resources, it was derived in the analysis.
In RTIC we don't aim for full program analysis (re-parsing all Rust is out of the scope here), so deriving resource usage and call structure is not possible. Nevertheless we could declare
sync = [c]
in the task attribute and havecx.sync.c(some_arg)
, to achieve this type of re-factorisation. Not sure if its a common enough pattern to make it worth implementing.The text was updated successfully, but these errors were encountered: