11.10.1.1 Warnings about possible module incorrectness

--no-warn-nothing-exported

Do not warn about modules which export nothing.

--warn-unused-imports

Warn about modules that are imported but not used.

--no-warn-interface-imports

Do not warn about modules imported in the interface, but which are not used in the interface.

--warn-interface-imports-in-parents

Warn about modules that are imported in the interface of a parent module, but not used in the interface of that module.

--no-warn-stdlib-shadowing

Do not generate warnings for module names that either duplicate the name of a module in the Mercury standard library, or contain a subsequence of name components that do so.

--no-warn-duplicate-abstract-instances

Do not warn about duplicate abstract typeclass instances. (Duplicate concrete typeclass instances are errors, and are always reported.)

--warn-too-private-instances

An instance declaration has to be private if it is for a private type class (meaning a type class that is not visible outside the current module), if some of its member types refer to private type constructors, or if its class constraints refer to private type classes or private type constructors. Such instances can only be relevant in the current module. Generate a warning if an instance declaration that can be relevant outside the current module is not exported.

--no-warn-subtype-ctor-order

Do not warn about a subtype definition that lists its data constructors in a different order than its supertype.