Fix scalar Blockwise in numba backend #1846
Merged
+69
−13
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.
Closes #1760
Inner functions of Blockwise will always get 0d arrays and not scalars, unlike Elemwise/RandomVariable inner functions.
This is also what the python impl of Blockwise already did, although it's not what numpy
vectorizedoes. AFAICT there's no syntax to distinguish, but 0d array should be more robust (if more wasteful). It will also avoid numba/numba#10358Most Blockwise Ops shouldn't have scalar inputs, or if they do, the cost of accessing them shouldn't dominate the runtime.
Cherry picked from #1806