Repository navigation
Fix incorrect @SideEffectsOnly indices in BitSet, StringLatin1, and StringUTF16 - #302
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configuration
📒 Files selected for processing (3)
Included review availability: This review used your included allowance. Your plan provides up to 1 included review per hour; 0 remain after this review. 📝 WalkthroughWalkthroughThe changes update Priority: ➖ Normal Change: Bug fix · Severity of issue fixed: Medium Merge Risk: ⚪ Minimal · up to The annotations now identify the objects these methods mutate, without changing runtime behavior. No actionable merge risk remains. Security Architecture ReviewSecurity architecture risk: ⚪ Minimal · up to The corrected annotations identify the objects these methods already modify. Method signatures and implementations remain unchanged, and the review found no material security risk introduced or worsened by this correction. Retained concerns Security review detailsSecurity Blast Radius
🚥 Pre-merge checks | ✅ 1 | ❌ 2❌ Failed checks (2 warnings)
✅ Passed checks (1 passed)
Full details: Out of Scope Changes checkExplanation The
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Fixes typetools/checker-framework#8325.
BitSet.clear(),clear(int), andclear(int, int):@SideEffectsOnly("#1")→@SideEffectsOnly("this").#1does not exist forclear()and is anintfor the other two; all three mutate the receiver.StringLatin1.getCharsandStringUTF16.getChars:@SideEffectsOnly("#3")→@SideEffectsOnly("#4").#3isint srcEnd;#4is thechar[] dstthat is written.The test case is in the companion checker-framework pull request: typetools/checker-framework#8326