Bug 166 – Proposed new Bugzilla keywords: undefined, warning

There's been no comment on the newsgroup about using Bugzilla to propose enhancements to the Bugzilla installation, so I'm guessing nobody minds. I'd like to suggest a few new keywords: undefined - for bugs where correct compiler behaviour isn't clear from the spec. This could cover both where the point of the bug report was to point out an ambiguity or inconsistency in the D spec, and where discussion on a bug has revealed that the spec isn't clear on the issue. warning - for bugs in DMD's (or GDC's) generation of warnings. An alternative to a single "warning" keyword would be separate keywords for false positives, false negatives and badly worded warnings, similar to "rejects-valid", "accepts-invalid" and "diagnostic" for errors, but I can't make up my mind if this detail is worth it.

There's already a keyword 'diagnostic' for warnings or errors. So, no need for a new 'warning' keyword, imho. I added a keyword 'spec' for issues surrounding the specification, though I'm tempted to suggest that this category of bugs belongs in a different component rather than in the DMD component. I'll leave things with the new keyword for now and it can easily be changed later as needed.

If the bug being reported is with the spec, then at the moment the www.digitalmars.com component is most appropriate, but the keyword will at least distinguish issues with the language spec from other issues relating to the website. OTOH if the reported bug is with the compiler, then it can also have the 'spec' keyword (at least in the scheme as I see it). This is likely a compiler crash or generation of code that can't be considered correct, but for which the correction cannot be established by reading the spec. If we had "Specification" as a component instead of a keyword, then it would raise the question of what to do with bugs of the latter type. Two possibilities: - reclassify the bug under Specification, thereby making it seem less important that the compiler already behaves badly - file a second bug for the hole in the spec itself, and make the compiler bug depend on it

dlang/dlang-bot pull request #271 "Fixes so far" was merged into master: - e4775e9412f288818d94efe5f7a9f3baf4f8e3a3 by Vladimir Panteleev: Cache GitHub API requests Cache hits do not count against the API rate-limit, so it is always beneficial to do so. The caching code is reused from https://github.com/CyberShadow/DAutoTest/blob/master/github.d and https://github.com/CyberShadow/ae/blob/next/net/github/rest.d, though it omits the redirect handling code (which is also added in the following commit). Fixes #166. https://github.com/dlang/dlang-bot/pull/271