[lang] Make the closure serializable. #888
Merged
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.
In order to enable the scope to pass from one SRE kernel to another SRE kernel, the scope's closure must be serialized without the enclosing object (agent, behavior, etc.). In other words, only the scoping function and the values that are used into this functions must be serialized.
This PR fixes the
SarlCompiler
for generating a proxy class for each serializable closure. This proxy contains only the data that are used into the closure, without reference to the enclosing types of the closure.see #885
Signed-off-by: Stéphane Galland galland@arakhne.org