Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Always use "faster" in effect size summary #144

Merged
merged 2 commits into from
Jun 4, 2021

Conversation

fitzgen
Copy link
Member

@fitzgen fitzgen commented Jun 4, 2021

A faster value less than 1 is actually slower, but to say "0.7x slower" isn't
correct, and actually means the opposite.

Fixes #141

A faster value less than 1 is actually slower, but to say "0.7x slower" isn't
correct, and actually means the opposite.

Fixes bytecodealliance#141
@fitzgen fitzgen requested a review from cfallin June 4, 2021 20:51
@fitzgen
Copy link
Member Author

fitzgen commented Jun 4, 2021

The CI failure is fixed by the third commit in #143.

Copy link
Member

@cfallin cfallin left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Awesome, thanks!

Not sure how things were working before...
@fitzgen fitzgen merged commit f0835a8 into bytecodealliance:main Jun 4, 2021
@fitzgen fitzgen deleted the faster-slower-wording branch June 4, 2021 22:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Faster/slower summary messages are confusing: invert one of the adjectives or one of the ratios
2 participants