Remove exposing (..) for imports

[evuez]

Fixes #76

@robinheghan is the goal to also remove internal usage of import ... exposing (..)? Seems like this is used for Basics.

[robinheghan]

Thank you for looking into this, @evuez !

The compiler still needs to say that everything from Basics is imported, as I don't want there to be a tighter integration between the core package and the compiler than what we've already got.

Because it will still be possible to expose everything from a module definition, there should be a good error message for when people want to import everything, would you like to take a stab at that error message as part of this PR?

I mostly work on Gren at fridays, so I won't do a code review or merge the PR until then, just so you know.

Thanks again for looking into this 🙏

[robinheghan]

@evuez I think your current approach looks good. :)

[evuez]

@robinheghan Sorry didn't have time to look more into that, was hoping to take a stab at the error message next week.

[robinheghan]

@evuez Just to let you know, I'm starting to focus on bug-fixes and documentation improvements in about a week. So if you want this to land in time for 0.2, you're starting to run out of time. :)