Skip to content

Add a warning for unknown modules that were compiled #381

Closed
bos opened this Issue May 24, 2012 · 3 comments

3 participants

@bos
Haskell member
bos commented May 24, 2012

(Imported from Trac #388, reported by jcpetruzza on 2008-11-01)

Let's say you are working on a new version of a library; you add a new internal (i.e. non-exposed) module but you forget to update the package description. You locally test your changes, everything works fine so you install it. Now, since the new module is not listed in other-modules it will not be included in the final library. Therefore, when you try to use it you get rather cryptic linker errors. It can take a while until you realize where the problem is coming from.

The proposal is to look, during build, for compiled modules under the dist directory that are not included in the final library and warn the user about their presence.

@bos
Haskell member
bos commented May 24, 2012

(Imported comment by @dcoutts on 2008-11-01)

Interesting approach.

For anyone who wants to try implementing it, watch out for old stale .hi files in the dist directory. Perhaps comparing timestamps or something will be enough.

@timthelion

#939 dup

@ttuegel
Haskell member
ttuegel commented Apr 23, 2015

Duplicate of #1746.

@ttuegel ttuegel closed this Apr 23, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.