Take a look at projects such as Scalaz and Cats in how they handle being able to chose which imports for syntax extensions are visible. AutoLifts is a combination of both syntax extensions and auto-lifting contexts but an end user shouldn't have to deal with 27 combinators unless they choose via importing autolifts.Cats._.
Goals should be:
Arrange imports so that there is a "core" of commonly used syntax like those found on standard Scala collections (liftMap, liftFlatMap, liftExists, etc.)
Potentially look into dividing things via type classes in keeping with the backing libs
Take a look at projects such as Scalaz and Cats in how they handle being able to chose which imports for syntax extensions are visible. AutoLifts is a combination of both syntax extensions and auto-lifting contexts but an end user shouldn't have to deal with 27 combinators unless they choose via importing
autolifts.Cats._.Goals should be: