It's always possible to get NaNs and Infs.
We can't check for those after every opcode, as it's kinda costly. But we could add a debug "nancheck" unit that checks if the current signal is nan / inf and errors with a helpful message where the nan / inf occured.
User could disable them as needed and they would certainly not be compiled in into the final version.
It's always possible to get NaNs and Infs.
We can't check for those after every opcode, as it's kinda costly. But we could add a debug "nancheck" unit that checks if the current signal is nan / inf and errors with a helpful message where the nan / inf occured.
User could disable them as needed and they would certainly not be compiled in into the final version.