It would also be more correct since pow returns a double, which gets imprecise at n = 94906269.

Damnit I spent so long looking for an equivalent function for nCr and it was right there 😔

You can use the inclusive range operator ..= rather than .. to get rid of the +1

Hey, samesies! I don't quite see the point of converting the vec to a tuple, since it just changes how you access the elements, but eh

Probably because this was written many years ago, and there was no built-in implementation of IntoIterator for [T; 13] at the time.

that's right, check out the fork

Why would you do for &(n, symbol) in symbols.iter { instead of just for (n, symbol) in symbols {?

You know I feel like that array could've been constructed somewhat more concisely. You never know though

yeah, how it is now doesn't match the description
Equal functions should result in False because some intersection points are outside the interval (unless the interval is all real numbers).

Great puzzle, but the description needs to be more clear on what is expected, maybe adding some more examples of expected output. Specifically, that two equal functions should return True, and two functions that don't intersect should return False.

Yeah, how returning pointer to stack got top score in best practices is beyond me...

Instead of breaking just to return list straight after, you can just replace break with return list