Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Add a new benchmark, tuple-stress. #23
This benchmark stresses the compiler in interesting ways and I think it's worth including.
The name follows existing precedent even though I don't much like that precedent, because it results in long names with common prefixes that are a pain to tab-complete :(
The time to compile with a trunk rust is 4.1s on my machine.
I don't believe the precedent makes much sense either; I think renaming this to something more like "big array of tuples" (though possibly not "big" since IIRC there's another benchmark with that name). We can include the issue information and other metadata as comments in the makefile or in the main source; or introduce a README in each directory documenting why that test is there and what it's intended to test. It's possible we can later convert some of that information to something shown on the site itself, too.