Deprecate and remove seqMap

Open treeowl opened this issue 7 years ago • 2 comments

seqMap appears to be the only reason parallel depends on containers. It would be nice to be rid of it. The obvious replacement would be seqBifoldable. I'll have to add a Bifoldable instance for Data.Map, but that won't be a problem.

Jun 02 '18 22:06 treeowl

is there a problem with containers dependency? it comes with ghc anyway, no?

Jun 03 '18 00:06 Fuuzetsu

@Fuuzetsu, it does, but parallel is also a core library. When building GHC, fewer dependencies among core libraries can allow more parallelism in the build process. I don't know how much it matters in this particular case.

Jun 03 '18 02:06 treeowl