[Python] UDFs now produce the correct result when used together with range
#7876
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.
This PR fixes #7773
The title might be too narrow, but I was struggling to find a good concise explanation of what the issue was.
Because the function was not marked as having side effects, ConstantFolding caused us to only execute the function once.
After that was fixed though, in the c++ wrapper for the python udf execution we turned it into a ConstantVector if all the inputs are constant, which made udfs like this produce the wrong result: