6 Jan
2015
6 Jan
'15
11:36 p.m.
Do we need a separate compatibility package for just this function?
Not many people will want to try to roll their own.
On Tue, Jan 6, 2015 at 6:30 PM, Eric Mertens
There's no option which avoid needing to fix all packages on hackage, so each maintainer using this function will be responsible for fixing his packages.
If we fix it in place everyone needs to add CPP to avoid calling the broken version on old versions of directory and use an alternative implementation.
If we make a new function everyone needs to conditionally call the new function or use an alternative implementation.