Frits van Bommel wrote:
Walter Bright wrote:
Christopher Wright wrote:
Walter Bright wrote:
Christopher Wright wrote:
Additionally, the compiler has sufficient information to complain
about the problem at compile time, but it doesn't. That is a bug.
No, it does not. The compiler doesn't know about private imports of
separately compiled modules.
Okay, the compiler could gain that information, but it does not,
since it is not required. In many cases, the compiler could detect
these issues. Detecting these would be a reasonable, if low priority,
enhancement.
The problem if it detects it in an implementation-defined manner is
the source code is no longer portable.
... If the result of compilation provably won't *run* anyway, what's the
problem with a compile-time error?
Right. It's like the compiler warning you if your program starts with
"assert (false)".
