Fixes #16 (at least the bits to do with $0.1.1.1.1.1 being a pain).
I had to split the tests up like that to get the thing to compile in under a minute, and, crucially, to keep it from heating my laptop up to the point where it burnt my leg through thick denim.
Basically, just never parse expressions of any kind with more than ~3 terms. Break them down and map them til you have 3-tuples or smaller. Swift can’t deal with more than that right now.
robrix
commented
9 years ago
Fixes #16 (at least the bits to do with
$0.1.1.1.1.1being a pain).I had to split the tests up like that to get the thing to compile in under a minute, and, crucially, to keep it from heating my laptop up to the point where it burnt my leg through thick denim.
Basically, just never parse expressions of any kind with more than ~3 terms. Break them down and map them til you have 3-tuples or smaller. Swift can’t deal with more than that right now.
This is ridiculous.