[VHRanger]

There's a learning curve. It only works when the `@jit(nopython=True)` doesn't reject compilation.

Otherwise it's no better than python.

Generally numba works the same way writing C works: you pass in raw buffers (numpy arrays) and do processing directly on those buffers. That compiles to good LLVM bytecode and is fast.

[pbowyer]

> There's a learning curve. It only works when the `@jit(nopython=True)` doesn't reject compilation.

Is there a way to get it to tell you when it rejects compilation? I don't recall one at the time (this was ~4 years ago) and spent a week and a bit trying to get it to work.