Will Core Data Support Cursor‑Based Pagination in Upcoming Xcode Releases?

Background

Core Data’s NSFetchRequest exposes fetchLimit and fetchOffset for pagination. While these map to SQL LIMIT and OFFSET, they become inefficient on tables with thousands or millions of rows, especially when the underlying store is SQLite. The current APIs also lack a stable cursor mechanism, so changing data between paged requests can lead to duplicates or gaps.

Unresolved Decision

Apple has not announced any cursor‑based pagination features for Core Data. The community wonders whether future Xcode releases will introduce such an API to address scalability and consistency concerns.

Questions

1. Which Xcode version would need to introduce cursor‑based pagination for Core Data?
2. What changes would be required in NSFetchRequest to expose cursor semantics?
3. Will the existing @FetchRequest property wrapper in SwiftUI adapt to cursor‑based pagination?