Siu Kwan Lam
Siu Kwan Lam
the problem seems to be at https://github.com/numba/numba/blob/main/numba/core/typing/context.py#L620 and `allows_ambiguous` is `True` when resolving `add()` in `add_caller()`.
turning off the ambiguous overload leads to error like: ``` TypeError: Ambiguous overloading for (uint64, int64): (float64, float64) -> bool (complex128, complex128) -> bool ``` in the testsuite. So, `eq(uin64,...
Note: - check typeof logic in dispatching. seems like it's always picking intp.
`nrt_external.h` from https://github.com/numba/numba/pull/4554 should satisfy the usecase for this.
Is this still needed?
> @sklam is this intended for 0.57? Sure. We already dropped py
> This is comment, but it seems like it is a "dead comment" now: > > https://github.com/numba/numba/blob/main/numba/tests/test_withlifting.py#L1109-L1110 changed in https://github.com/numba/numba/pull/7920/commits/d2d76a663bcbb7d0df4eb0b81176f425362ee2ff > > This could be made more precise by using...
@esc, can you approve this PR please?
There are two different ideas here: 1. `cfunc` doesn't respect `NUMBA_DISABLE_JIT=1`. That's something we can fix by wrapping the function with `ctypes.CFUNCTYPE` so the interpreted python function is exposed as...