Currently after a cuda assert in a REPL such as jupyter notebook, it’s necessary to restart the REPL since cudaDeviceReset() isn’t called after the assert. This makes it rather hard to prototype in such an environment, since every bug requires a complete restart!
Is there any reason not to always reset after a cuda assert? If this isn’t a trivial change, perhaps you at least surface a python wrapper for cudaDeviceReset() we could call from python code?