Fix for file-private definitions output. This was an issue when using imports in the main package scope if the externally visible definition was a function, variable or namespace.
Added a warning if using file-private definitions when the main definition is a variable. This seems highly unusual as a real use-case, and is probably not going to work in the same way as it can for function and namespace (based on local testing and observation)
3 files changed