Emergency Self-Construct

@ricardoV94 thank you for posting this. I can reproduce easily and have labelled this accordingly. ``` esc@artemis [numba_3.13] (git)-[main] ~/git/numba-issues/numba/10266 python 10266.py Traceback (most recent call last): File "/Users/esc/git/numba-issues/numba/10266/10266.py", line...

@eoincondron thank you for opening this. Can you fix the `flake8` issues reported by CI?

@ngoldbaum thats awesome! So cool to see that it will work! I'll confer with the other maintainers during our weekly meet tomorrow and get back to you with suggestions for...

@swap357 @ngoldbaum great to see this move forward! I was going to mention that, the discussion during the developer meeting was fruitful, however we would not have accepted a GHA...

@NiankSoft thank you for the reproducer. I can confirm I see the same. Not sure what the cause is here. I might make sense to try to shrink the reproducer,...

I've updated the reproducer to give better diagnostic output: ```python from numba import jit from numpy import empty, random, uint64 from numpy.typing import NDArray from enum import IntEnum rng =...

If I had to guess, I would say that this is SSA related. Next step would be to look at the Numba IR for this.

@NiankSoft we discussed this during the developer meeting today. This turned out to be a type unification problem. Numba doesn't support type annotations and you need to cast `0` explicitly:...

> In my real setup, `val` is initialized to an element of `arr`: > > val: uint64 = arr[i]["word"] > > I would have expected the type to pass through...

@NiankSoft oh, in this case it was the `+` that is causing the issue: ``` esc@artemis [numba_3.13] (git)-[main] ~/git/numba-issues/numba/10261 gid diff --git i/numba/10261/10261_002.py w/numba/10261/10261_002.py index 8e69381443..c642a0cb42 100644 --- i/numba/10261/10261_002.py +++...