[Foundation] Cache NSObject user type classification. - #26555
Conversation
Adapt the prototype to the current NSObject lifecycle and use clearer flag names. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Copilot-Session: c1ed53e7-2f3b-449d-b812-00b6cce420a7
✅ API diff for current PR / commitNET (empty diffs)✅ API diff vs stableNET (empty diffs)ℹ️ Generator diffGenerator Diff: vsdrops (html) vsdrops (raw diff) gist (raw diff) - Please review changes) Pipeline on Agent |
🚀 [CI Build #4196fb0] Test results 🚀Test results✅ All tests passed on VSTS: test results. 🎉 All 264 tests passed 🎉 Tests counts✅ assembly-processing: All 1 tests passed. Html Report (VSDrops) Download macOS tests✅ Tests on macOS Sonoma (14): All 5 tests passed. Html Report (VSDrops) Download Linux Build VerificationPipeline on Agent |
Cache whether an NSObject instance represents a user type in the object's existing native-backed flags.
This avoids repeating the class lookup and taking the global user-type cache lock when releasing an object. Invalidate the cached value when the native handle changes, and preserve current error handling for invalid handles.
Update the preserved-API baselines for the new helper and flags.
🤖 Pull request created by Copilot