Create a completeness breakdown chart with benchmarks

[jreina]

Create a chart comparing ShittyLINQ.js to System.Linq showing whether or not ShittyLINQ.js has a given method. If a method exists, provide a benchmark for the method in both assemblies showing the performance difference. Describe your methodologies.

[the-pat]

I'll take this one.

@jreina and @jakehamtexas, what do y'all think about using GitHub actions to update the benchmarks? The Continuous Benchmark action seems pretty useful for this purpose. Thoughts?

[jkhmtx]

I like the idea of doing this in a CD context. But holy moly, this issue looks like it would scale pretty steeply with the size of the library increasing. For each method you would need -

1. A benchmark test case defined
2. A way to dynamically invoke the test case in both assemblies (presumably the same runtime)

The problems could really start cascading at this point. This is integrating some test surface areas that haven't been previously considered - especially fidelity to the LINQ function signature. If the function signature in both assemblies is not exactly the same, you could be stuck eating somebody else's bad implementation when you have to fix a compiler error to get your test case to run.

Maybe adding test cases would be better suited to their own issues, and creating a script/scaffold for adding the test cases and displaying them in doc would be a good standalone issue.

@the-pat @jreina