Oom alloc
Was it intentional that fn from_sparse assumes cells are in (row, col) order? This test example demonstrates this is not always the case and OOM allocates due to an overflow.
~~Based on #462~~ restructured history
Added another example that OOMs, hasn't been fixed yet, I'm working around it for my usecase by using unstable set_alloc_error_hook
Thanks! Tiny comment just to help future debugging if needed.
Do you mean a comment explaining the last OOM file that was added?
I've added a FIXME to the function call that OOMs, if this was not what was meant please advise further. This is ready to merge imho.
Curious whether you know anything about the unknown record types as mentioned in #462. The commit history was starting to look complex, so I folded it into this PR.