Allow the user to "connect" R and M2 variables that should maintain the same value, and m2r can update these values before/after each call to m2(). If done correctly, it would behave as if the variables share the same memory.
Some thins to note.
This feature would add significant overhead, as the list of "active" pointers would need to be checked and updated before and after each m2() call.
This feature would likely require modifying the protocol to allow metadata to be passed back and forth with each m2() call. This should be done anyway, to make the interface more extensible.
This feature would hinge on the use of synchronous calls, and would likely be impossible if asynchronous calls were added.
coneill-math
commented
5 years ago
Allow the user to "connect" R and M2 variables that should maintain the same value, and m2r can update these values before/after each call to
m2(). If done correctly, it would behave as if the variables share the same memory.Some thins to note.
m2()call.m2()call. This should be done anyway, to make the interface more extensible.