Re: [Haskell-cafe] Deprecation being transitively reported for re-exported definitions

Ivan mentioned that option in his email—seems like that could be okay (but awkward!) for functions, but would not work well for other definitions like typeclasses. On Sat, Aug 14, 2021, 18:44 Viktor Dukhovni wrote:

...

On 14 Aug 2021, at 9:22 pm, Ivan Perez wrote:

I have a library that is exposing too much. As a minimal example, say the library contains: - Module A, which defines several functions and types. - Module B, which exports specific definitions from module A and has none of its own.

The simplest solution might be:

module B (somefunction)

import qualified A

somefunction = A.somefunction

This creates a *new* function in B, which is not deprecated, without re-exporting anything from A.

-- Viktor.

_______________________________________________ Haskell-Cafe mailing list To (un)subscribe, modify options or view archives go to: http://mail.haskell.org/cgi-bin/mailman/listinfo/haskell-cafe Only members subscribed via the mailman list are allowed to post.