While making this PR, I noticed the test setup in math/big involves a library build and checking against Python's implementation. I renamed the package to conform to the convention of the rest of the tests, but I've otherwise left it alone. I'm not sure if the library build should be moved, since it does not have any @test procs on it.
After several years of math/big it's tested well enough that it could be used as an oracle for later self-tests, but when I wrote it it made sense to test against Python. :-)
While making this PR, I noticed the test setup in
math/big
involves a library build and checking against Python's implementation. I renamed the package to conform to the convention of the rest of the tests, but I've otherwise left it alone. I'm not sure if the library build should be moved, since it does not have any@test
procs on it.