Fix a problem where Object.callv() and Callable.callv() would not correctly invoke when a read-only Array was passed. #915
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.
As mentioned in the title, I made a small patch because the behavior was unexpected in the following case:
When passing a read-only Array, every
argptrs
in callv() address to same memory, so in cases where the bad conditions within callv() are met, I changed it to copy the arguments.redot-engine/core/variant/array.cpp
Lines 100 to 114 in 106ba51
It would be more appropriate to modify Array or ScriptInstance::callp(), but in that case, the impact would be extensive so this is a mitigation measure.