Re: `import foo {.private.}` to allows access to private fields (eg: package-level visibility)

[zahary]

Private imports would create their own set of conflicting requirements for the 
goals of incremental compilation. You wouldn't be able to cleanly separate the 
public interface of a module from its private components that should not 
trigger a rebuild upon changing.