@burntsushi5 woah just saw cargo-benchcmp; tyvm for actually making this!
Question: why a "multiple files" workflow vs "multiple commits"?
-
-
Replying to @Gankra_
:-) I use it during development where I'm constantly tweaking things to see how they change. Far below the granularity of the commit
1 reply 0 retweets 1 like -
Replying to @burntsushi5
Ah I was basically thinking of comparing HEAD to the current workspace. Does that not match what you're describing?
1 reply 0 retweets 0 likes -
Replying to @Gankra_
Does not match. :-) It is iterative. Make a change -> check bench. Make another change -> check bench again. And so on.
1 reply 0 retweets 0 likes -
Replying to @burntsushi5
I guess it's not clear to me how you can easily capture that flow with the given method; aggressively copy-pasting code?
1 reply 0 retweets 0 likes -
Replying to @Gankra_
edit: add optimization, run: bench > a, edit: tweak optimization, run: bench > b, compare: cargo benchcmp a b
1 reply 0 retweets 1 like -
Replying to @burntsushi5
ohhhh I totally misunderstood from my first reading. You just store the results and then have benchcmp compare the numbers.
1 reply 0 retweets 0 likes -
Replying to @Gankra_ @burntsushi5
Ok this makes way more sense and seems real solid.
1 reply 0 retweets 1 like -
Replying to @Gankra_ @burntsushi5
for whatever reason I parsed "save benchmarks to a file" as literally saving the #[bench] code to its own file.
1 reply 0 retweets 1 like
LOL. Ah. Yes. Actual operation is much simpler. :-)
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.