Closed kbrock closed 4 years ago
Haven't had to type an encoding in eons...
# encoding: utf-8
It looks great.
I removed compare from the mix. just made it too complicated.
Instead, I can create a PR just for compare but guidance is suggested.
I merged #90 so this has a conflict now. As for how to deal with compare!, I’d prefer to delegate it to the report itself.
kicking. odd bundler errors
trying again. seeing if there was a blip, or something is wrong at the core
@kbrock Still want to get this merged? I can help.
Hi @nateberkopec
I don't think I'll use this functionality. I thought it helped clean up the code but hard to say that with +73/-24
If you like the changes, then I'll make what ever updates you want. Otherwise I can close.
Please leave open for now - I'll take another look!
@nateberkopec let me know if you want me to move stuff around here or introduce just part for another PR
Feel free to copy anything or ignore. Just trying to help
I don't really know why I closed this tbh
lol
This was in reaction to wanting all output to be via a consistent channel. A simple @out=STDOUT
would probably have been good enough.
The implementation was a little buggy as determining whether to output some of the output in the various modes did not quite match the current behavior.
Also, to be honest - the feature was not for me. I use other means of capturing the metrics
This unifies the double
@stdout
and@suite
calls. It also allows a user to choose a different output.Addresses #81 for
warmup
andbenchmark
but notcompare!
Outstanding:
Changing
compare
is not as easy, the output needs to be passed in:@outs
config
and use that throughoutStdoutReport
and changecompare
to use the@outs
.Let me know which you approach you prefer. I can fixup this PR or just make another.
Sample Code