-
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
Avoid needless memory slot in allocator #836
Comments
For a write statement, an allocation is not needed if the object to be written is a simple variable. Taking this case into account in the allocator.
The special handling of Write statements will most probably be obsolete after implementation of #807. Write (as well as Read statements) will have to be in a separate state and refer to a global variable. Using a message aggregate inside a Write statement will not be supported anymore. So we can defer this issue until #807 is merged and then remove the extra allocation for Write statements completely. |
Never mind, I did not see that you already created a PR for that. I just thought we could prevent unnecessary work, but as it is already fixed, we can also merge it now. |
For a write statement, an allocation is not needed if the object to be written is a simple variable. Taking this case into account in the allocator.
The allocator currently systematically allocates a memory slot for Write statements that involve messages, but such a slot is not always needed. I will refine the condition to allocate the slot to represent the need of the session generator.
The text was updated successfully, but these errors were encountered: