Cabal confusion. Modules not being exposed still accessible for testing.
I use reactive-banana https://github.com/HeinrichApfelmus/reactive-banana/blob/master/reactive-ban... as an example. My question is how can Reactive.Banana.Internal.Combinators be testable from Reactive.Banana.Test.Plumbing? My misunderstanding is that only modules named in the exposed-modules stanza could be imported. Could someone clear up my misunderstanding?
Michael Litchard writes:
I use reactive-banana https://github.com/HeinrichApfelmus/reactive-banana/blob/master/reactive-ban... as an example.
My question is how can Reactive.Banana.Internal.Combinators be testable from Reactive.Banana.Test.Plumbing? My misunderstanding is that only modules named in the exposed-modules stanza could be imported. Could someone clear up my misunderstanding?
The shared "hs-source-dirs" means the test suite is re-compiling the file from source, not depending on the library. Anthony
Ah thanks!
On Wed, May 4, 2016 at 4:24 PM, Anthony Cowley
Michael Litchard writes:
I use reactive-banana < https://github.com/HeinrichApfelmus/reactive-banana/blob/master/reactive-ban...
as an example.
My question is how can Reactive.Banana.Internal.Combinators be testable from Reactive.Banana.Test.Plumbing? My misunderstanding is that only modules named in the exposed-modules stanza could be imported. Could someone clear up my misunderstanding?
The shared "hs-source-dirs" means the test suite is re-compiling the file from source, not depending on the library.
Anthony _______________________________________________ Haskell-Cafe mailing list Haskell-Cafe@haskell.org http://mail.haskell.org/cgi-bin/mailman/listinfo/haskell-cafe
participants (2)
-
Anthony Cowley -
Michael Litchard