
(Disclosure: I'm the author of tasty.)
If there are people who are willing to keep test-framework on life
support, it's definitely useful. Let's keep those revdeps from breaking.
However, if someone is considering adding new features, I'd encourage
them to look at tasty instead. It has a cleaner and smaller code base
and is more extensible, but otherwise is very similar in spirit to
test-framework.
Roman
* Greg Weber
sorry, I didn't understand what the original message was about. I was talking about a long-term direction
On Tue, Oct 8, 2013 at 7:09 PM, Bryan O'Sullivan
wrote: I don't really care about that goal, to be honest; in this case, I just want a minimal number of existing packages to break when GHC 7.8.1 is released.
On Tuesday, October 8, 2013, Greg Weber wrote:
I would like to reduce the amount of test framework fragmentation. A better path forward might be to use the newer more extensible and well maintained tasty package. I am imagining it is trivial to create a compatibility layer with the previous test-framework or to find and replace, but that might not be the case.