-nodraftCompile enables -Xnamespace PACKAGE by mistake

[niloc132]

Boolean flags come with the option of prefixing them with no to do their opposite, but the -draftCompile flag doesn't consider the boolean value when controlling the namespace handling.

Steps to reproduce:
Compare the compiled output of a "production" build, with and without -nodraftCompile. Add the flag as early as possible, so that other args can override any defaults it happens to set (e.g. if a different optimization level is desired, etc).

Expected:
The two sets of compiled output are nearly or exactly the same

Actual:
The "nodraftCompile" output is larger than the other (real world example, 1.8MB without the flag, 2.1MB with the flag, more than 15% bigger than it should be).

Workaround:
Explicitly assign the -Xnamespace command line arg to NONE - this restores it to the expected value.