Hoopl collection classes could use enummapset?

I have found myself using https://hackage.haskell.org/package/enummapset a lot in my code. It provides wrappers around `IntSet`/`IntMap` that uses `Enum` rather than `Int`, which allows for better type safety.

Now I am doing more work with Hoopl in my project and it lacks certain useful functions from `IntMap`. I am looking at `restrictKeys` at the moment. I am trying to wrap my head around how to implement it, but I also realize that in some way this collection code in Hoopl is just the same thing as is also provided by enummapset. I was thinking that maybe it would better to migrate the code in Hoopl to make use of enummapset rather than rolling its own duplicate that tends to be out of date (I have added some missing functions before).

I wonder what the maintainer and people using Hoopl think about this?

Start by reading Hoopl's collection code and comparing it with the enummapset package, focusing on the missing restrictKeys functionality and the existing IntMap/IntSet wrappers. Review the discussion and determine whether migrating Hoopl to enummapset is appropriate; done requires an agreed migration direction and a complete, compatible collection implementation.

Written by the indexing model from the issue text.