[typetools/checker-framework] b1a954: Explain why some JavaExpression parse failures are...

0 views
Skip to first unread message

Michael Ernst

unread,
Aug 21, 2026, 10:44:12 AM (4 days ago) Aug 21
to checker-fr...@googlegroups.com
Branch: refs/heads/master
Home: https://github.com/typetools/checker-framework
Commit: b1a9545b1ab7e47e376caa8f7fc4a2ff40ace516
https://github.com/typetools/checker-framework/commit/b1a9545b1ab7e47e376caa8f7fc4a2ff40ace516
Author: Michael Ernst <mer...@cs.washington.edu>
Date: 2026-08-21 (Fri, 21 Aug 2026)

Changed paths:
M annotation-file-utilities/src/main/java/org/checkerframework/afu/scenelib/util/coll/WrapperMap.java
M checker/src/main/java/org/checkerframework/checker/index/inequality/LessThanAnnotatedTypeFactory.java
M checker/src/main/java/org/checkerframework/checker/index/samelen/SameLenTransfer.java
M checker/src/main/java/org/checkerframework/checker/index/upperbound/UpperBoundAnnotatedTypeFactory.java
M checker/src/main/java/org/checkerframework/checker/index/upperbound/UpperBoundVisitor.java
M checker/src/main/java/org/checkerframework/checker/resourceleak/MustCallConsistencyAnalyzer.java

Log Message:
-----------
Explain why some JavaExpression parse failures are not reported (#8031)



To unsubscribe from these emails, change your notification settings at https://github.com/typetools/checker-framework/settings/notifications
Reply all
Reply to author
Forward
0 new messages