-
-
Notifications
You must be signed in to change notification settings - Fork 153
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
Fix storage and mit-mot handling in numba_funcify_Scan
#1203
Fix storage and mit-mot handling in numba_funcify_Scan
#1203
Conversation
34d8080
to
fd03bd5
Compare
Codecov Report
Additional details and impacted files@@ Coverage Diff @@
## main #1203 +/- ##
========================================
Coverage 79.13% 79.14%
========================================
Files 173 173
Lines 48492 48523 +31
Branches 10966 10319 -647
========================================
+ Hits 38374 38403 +29
- Misses 7625 7628 +3
+ Partials 2493 2492 -1
|
While working on this, I noticed some inner-function typing issues that—again—involve the distinction between NumPy and Numba scalars (cf. #1063). More specifically, an inner-function could return a Numba scalar for a tap with storage that is typed as a NumPy scalar. If I can find a reasonable general solution soon, then I'll include it in this PR; otherwise, we can merge this and handle that issue separately. |
ae3ef98
to
d3703b2
Compare
c2aadda
to
f2c509f
Compare
This should prevent errors when the input is already a Numba scalar, and it will use Numba's type information to selectively apply the scalar conversion.
Using the `auto_name` values will result in cache misses when caching is based on the generated source code, so we're not going to use it.
f2c509f
to
aefeeef
Compare
numba_funcify_Scan
numba_funcify_Scan
This PR fixes some storage allocation and access/usage issues in
numba_funcify_Scan
.Closes #923
Scan
input storage support