Summary
Sometimes there are undesirable warnings that the compiler prints anyway. For example, most PureScript projects break their internals to multiple files for their own reasons, but for the end-user this is nothing but a nuisance, so you typically want to import all project files by just the project name. But then the compiler starts spewing ImplicitQualifiedImport warnings.
In practice what happens then is that useful warnings get lost among those unwanted ones, so you don't know when there's actually something to fix in the code.
Related old discussion here
Motivation
Being able to turn warnings into errors, which is impossible to do when there are warnings you'd prefer not to fix.
Proposal
The compiler should provide an option similar to GCC's -Wno-FOO to suppress warning FOO.
Examples
purs --Wno-ImplicitQualifiedImport Foo.purs
Summary
Sometimes there are undesirable warnings that the compiler prints anyway. For example, most PureScript projects break their internals to multiple files for their own reasons, but for the end-user this is nothing but a nuisance, so you typically want to import all project files by just the project name. But then the compiler starts spewing
ImplicitQualifiedImportwarnings.In practice what happens then is that useful warnings get lost among those unwanted ones, so you don't know when there's actually something to fix in the code.
Related old discussion here
Motivation
Being able to turn warnings into errors, which is impossible to do when there are warnings you'd prefer not to fix.
Proposal
The compiler should provide an option similar to GCC's
-Wno-FOOto suppress warningFOO.Examples