private module stuff

[bearophile]

Sean Cavanaugh:

> 	So I was learning how to make a module of mine very strict with private 
> parts, and was surprised I could only do this with global variables and 
> functions.   Enums, structs, and classes are fully visible outside the 
> module regardless of being wrapped in a private{} or prefixed with 
> private.  Am I expecting too much here?

You are expecting the right thing. If you are right, then it's a bug that eventually needs to be fixed. Take a look in Bugzilla, there are several already reported import/module-related bugs.

Bye,
bearophile