If and when base is split, then just include Data.List.Split with whatever
package all the other List stuff gets put in. My point is, this module
should live in the same package where the other list functions live.
I'm in favor of splitting base, but things should not be so broken up to
the extreme of having a package just for left-pad. It is possible to find
middle ground.
-- Dan Burton
On Fri, Nov 2, 2018 at 10:49 AM Elliot Cameron
Ah in the context of splitting base this seems like a backward move. The solution must really be to have tooling that can pull in libraries with minimal friction.
On Fri, Nov 2, 2018 at 10:47 AM Henning Thielemann < lemming@henning-thielemann.de> wrote:
On Fri, 2 Nov 2018, Dan Burton wrote:
What about just adding Data.List.Split to base?
... and then splitting 'base'? :-)