You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Mar 15, 2023. It is now read-only.
It's very easy to mess up benchmarks when using Program.Benchmark, since the kernel feeds the output from benchmark run N to run N+1. This means we don't measure the exact same action on each iteration.
Ideally the kernel would fix this, but I'm not sure that is going to happen. I propose that Benchmark() checks that input == output, and raises an error otherwise.
It's very easy to mess up benchmarks when using Program.Benchmark, since the kernel feeds the output from benchmark run N to run N+1. This means we don't measure the exact same action on each iteration.
Ideally the kernel would fix this, but I'm not sure that is going to happen. I propose that Benchmark() checks that
input == output, and raises an error otherwise.