hohn/codeql
1
0
Fork 0
mirror of https://github.com/github/codeql.git synced 2025-12-16 16:53:25 +01:00
Code Issues Packages Projects Releases Wiki Activity
Files
54ac18092daa7abb973bcd42063a01771e38e04a
codeql/java/old-change-notes/2021-05-14-close-resource-leaks-improvements.md
Dave Bartolomeo fa40d59332 Move older change notes to old-change-notes 
Now that change notes are per-package, new change notes should be created in the `change-notes` folder under the affected pack (e.g., `cpp/ql/src/change-notes` for C++ query change notes. I've moved all of the change note files that were added before we started publishing them in packs to an `old-change-notes` directory under each language, to reduce the temptation to add new change notes there.

I'm working on a document to describe how and when to create change notes for packs separately.
2021-12-14 12:35:04 -05:00

420 B
Raw Blame History

lgtm,codescanning

  • The "Potential input resource leak" (java/input-resource-leak) and "Potential output resource leak" (java/output-resource-leak) queries no longer confuse java.io classes such as Reader with others that happen to share the same base name. Additionally the number of false positives has been reduced by recognizing CharArrayReader and CharArrayWriter as types that don't need to be closed.