Better re-export handling

[garyb]

Resolves #1244. Resolves #291 in a slightly different way too (if A explicitly imports values from B and then re-exports B, only the values it imported will be re-exported).

[garyb]

All green at last!

[paf31]

👍 Thanks!

Edit: Actually, after I cabal installed this, transformers test suite no longer builds - it complains about things not being in scope, but they should be because of module reexports. Not sure what's going on, but I think we should figure it out before releasing the compiler.

[garyb]

They run okay for me now, did you make those changes for v0.7.0-rc.2 after posting this?

The changes you made look right to me - you can't export a module anymore unless you import it, the reasoning for this being only the specific values imported into the current module are re-exported when you export a module.

[paf31]

The tests run ok? I get Unknown value callCC since callCC is imported via a module reexport in the tests. This is with what's on master.

[garyb]

Yep. Tried cleaning the output folder?

[garyb]

Yup, definitely works for me - I just installed the master version of psc on my Mac, and with a fresh checkout of transformers the tests run fine.

[paf31]

Yes, I just removed output and I get the same error. I'll reinstall psc to be sure.

[paf31]

Yes, I don't see module reexports in the externs files. Is that an issue?

[paf31]

Seems like it would be an issue if we want to support separate compilation without looking at original source files.

[garyb]

#1425 should sort that out.

[coveralls]

Changes Unknown when pulling 55ba265 on 1244-reexports into ** on master**.