| View Issue Details [ Jump to Notes ] | [ Issue History ] [ Print ] | ||||||||||||
| ID | Project | Category | View Status | Date Submitted | Last Update | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 0000511 | mercury | Bug | public | 2020-06-19 18:22 | 2020-06-19 18:22 | ||||||||
| Reporter | zs | ||||||||||||
| Assigned To | zs | ||||||||||||
| Priority | normal | Severity | minor | Reproducibility | always | ||||||||
| Status | assigned | Resolution | open | ||||||||||
| Product Version | |||||||||||||
| Target Version | Fixed in Version | ||||||||||||
| Summary | 0000511: missing warning with --warn-unused-imports | ||||||||||||
| Description | The versions of two compiler modules before the application of the attached diff contain unused imports that the compiler - warns about if --warn-unused-imports is NOT specified, but - does NOT warn about if --warn-unused-imports IS specified, which is the exact opposite of the expected behavior. The reason for this inversion is that warn_unused_interface_import in module_qual.qual_errors.m generates a less-informative error message that it disables if --warn-unused-imports is specified, on the grounds that the code in unused_imports.m, which implements --warn-unused-imports, will generate a more informative error message for the same issue. However, in these cases, unused_imports.m does not do so. | ||||||||||||
| Tags | No tags attached. | ||||||||||||
| Attached Files |
| ||||||||||||
 Relationships |
|
 Relationships |
| Notes |
|
| There are no notes attached to this issue. |
| Notes |
| Issue History |
|||
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2020-06-19 18:22 | zs | New Issue | |
| 2020-06-19 18:22 | zs | Status | new => assigned |
| 2020-06-19 18:22 | zs | Assigned To | => zs |
| 2020-06-19 18:22 | zs | File Added: DIFF.bug511 | |
| Issue History |