Companion code for paper "Imperative Functional Programs that Explain their Work", Wilmer Ricciotti, Jan Stolarek, Roly Perera and James Cheney, ICFP 2017, Oxford, UK
then this will implicitly raise a "Division by zero" exception. This exception is not recorded in a trace in any way, which makes it impossible for isExn to spot a raised exception. I wonder when does this become a problem, ie. when does this cause incorrect results. I'm unable to construct any testcase that would expose practical ramifications of this potential bug (possibly due to #47?)
If I say
then this will implicitly raise a "Division by zero" exception. This exception is not recorded in a trace in any way, which makes it impossible for
isExnto spot a raised exception. I wonder when does this become a problem, ie. when does this cause incorrect results. I'm unable to construct any testcase that would expose practical ramifications of this potential bug (possibly due to #47?)