DebugMode catch uninitialized storage
Often uninitialized memory contains a mixture of zeros and huge exponents.
A heuristic for detection would need to be written.
This could run on all the inputs to a computation (when moving them out of storage_map and into r_vals for example).
A heuristic for detection would need to be written.
This could run on all the inputs to a computation (when moving them out of storage_map and into r_vals for example).
Leave a comment
I don't understand what this would bring. When we have c code and python code, should catch error that one version don't init the value. In the case where there is no c code, yes it could be usefull, but I think that any sensible unittest writen would find this.
Can someone give an example that show why/when this is usefull? Otherwise I propose to move it to Milestone 'Hell freezes over'
Can someone give an example that show why/when this is usefull? Otherwise I propose to move it to Milestone 'Hell freezes over'