You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I don't think we have enough reason to expose these. They are not containers internals and are not required to use containers internals. They are used purely internally. Two of these, BitUtil and StrictPair, contain only trivial definitions.
Should we move them to other-modules?
The text was updated successfully, but these errors were encountered:
9fc8b45 exposed all internals "per Ed Kmett's request"
576fe49 hid internal utils except for BitUtil and BitQueue. treeowl wrote that these might be useful for users (Refactor internal modules #324 (comment)). According to Hackage search (https://hackage-search.serokell.io/), nobody is using StrictPair or BitQueue. There are two uses of BitUtil: arithmoi uses highestBitMask and enummapset uses bitcount, both of these are gone on HEAD.
We currently expose three such modules:
containers/containers/containers.cabal
Lines 75 to 77 in bb1ec48
I don't think we have enough reason to expose these. They are not containers internals and are not required to use containers internals. They are used purely internally. Two of these, BitUtil and StrictPair, contain only trivial definitions.
Should we move them to other-modules?
The text was updated successfully, but these errors were encountered: