Thank you. So far as I am concerned this is an oddity to pass on to you
rather than a show-stopper. Even if I had not modified my code to
parse/compile faster I could survive even an overight run to deal with the
big table I have because I can then use saveState to make a snapshot, and
I sort of only have to do that about once. So stick it somewher eon your
list but do not panic about it!
Arthur
On Sat, 16 Jul 2016, David Matthews wrote:
I suspect that this is a problem with the intermediate code optimiser. List
cells are converted into tuples (pairs) and there are lots of cases where
it is important to optimise tuples. Unfortunately this case isn't one of
them and it would be better to leave it alone.
Thanks for reporting this. I'm not sure when I'll have a chance to look at
this in detail.
David
_______________________________________________
polyml mailing list
[email protected]
http://lists.inf.ed.ac.uk/mailman/listinfo/polyml
