5 Mar
2018
5 Mar
'18
02:02
I didn't pinpoint it precisely, but it's clearly not _num.scm's fault if you are accidentally doing unsafe fx ops with arbitrary numbers :)
-- vyzo
On Mon, Mar 5, 2018 at 3:55 AM, Bradley Lucier lucier@math.purdue.edu wrote:
I’d be curious to know where in _num.scm that problem occurred.
Brad
On Mar 4, 2018, at 12:10 PM, Dimitris Vyzovitis vyzo@hackzen.org
wrote:
So the problem was indeed declaration leakage -- there was a (declare
(fixnum)) leaking to the rest of the program and crashing inside _num.scm,