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

[timothee]

> include foo does this kind of, just need to include it once in the program or 
> you get duplicates.

include (which is really like C's #include) is very different:

  * include it once in the program or you can get duplicates, as you said
  * no way to force full qualification, eg from foo import nil {.private.}