Use tasty-bench package itself - [opened]

[hasufell]

In GitLab by @Bodigrim on Jul 1, 2022, 08:21

Merges tasty-bench -> master

As discussed at Bodigrim/tasty-bench#35 (comment), Windows build runs fine out of the box now.

[hasufell]

In GitLab by @maerwald on Jul 2, 2022, 06:20

This introduces a dependency on tasty, which itself depends on optparse-applicative, which then pulls in all sorts of things. The package currently does not depend on tasty.

I'm not sure this is an improvement dependency-wise?

[hasufell]

In GitLab by @Bodigrim on Jul 2, 2022, 07:18

You are the boss, you decide :) No hard feelings.

I don't see depending on tasty as a downside: pretty much every other boot package uses it. Using a well-known framework eases new contributions. It's also more flexible (like, you can add inspection tests) and featurefull (e. g., you can run only a failing test or only a certain group of tests; test suite is not limited to a flat list).

And using full-fledged tasty-bench is even more valuable in my experience. Not only it is significantly less code for you to maintain, but it gives an ability to compare against baseline or use bcompare. I find these features invaluable for an actionable performance analysis.

[hasufell]

historical ref: https://gitlab.haskell.org/haskell/filepath/-/merge_requests/115