I seem to have fixed this bug, only to find another- the issue was that
I misunderstood what Cabal means by "exposed modules" upon exposing all
of the modules MainTypes uses, the problem resolved itself. I now have
another problem, having to do with importing the file from
$HOME/.hackmail, but
Oh- I see, so The portion of code I have to interpret is already
separated -- it's not even compiled. The only interpreted code is a
configuration file in the users home directory. It needs to import some
chunk of the library (namely, MainTypes and Deliverable) so as to be
able to export a sing
So, if I understand correctly, the interpreter is compiling
MainTypes twice?
No, the interpreter is trying to compile types that were already
compiled by the compiler when building your application. The resulting
types are incompatible.
Could this be a result of having two outputs (one ex
So, if I understand correctly, the interpreter is compiling MainTypes
twice?
Could this be a result of having two outputs (one executable and one
library) in my .cabal file? it _does_ compile those things twice... If I
create a second cabal file which separates these two different packages,
w
Hi
Just a wild guess but maybe the interpreter is recompiling (in
runtime) code that has already been compiled to build your application
(in compile-time). This may lead to inconsistencies since a type such
as HackMail.Data.Main.Types.Filter may refer to two different (and
incompatible) t
Hi
Just a wild guess but maybe the interpreter is recompiling (in
runtime) code that has already been compiled to build your application
(in compile-time). This may lead to inconsistencies since a type such
as HackMail.Data.Main.Types.Filter may refer to two different (and
incompatible) t
