Rob Ryan

I’m wondering if this is a result of the [`deinit`](https://github.com/bizz84/SwiftyStoreKit/blob/master/SwiftyStoreKit/InAppReceiptRefreshRequest.swift#L48): ``` deinit { refreshReceiptRequest.delegate = nil } ``` So, if `InAppReceiptRefreshRequest` is deallocated, the delegate is set to `nil` even...

The standard `NSOperation` completion block is called after the operation finishes. What this means is that other operations that are dependent upon the current operation will generally have started before...

Re your retiring of `NSOperation`, that's certainly fine. Personally, I've got no problems with `NSOperation` based solution (I think it's a really elegant way to manage dependencies, degree of concurrency,...

Just [`cancel`](https://developer.apple.com/reference/foundation/nsoperation/1411672-cancel?language=objc) an individual operation or [`cancelAllOperations`](https://developer.apple.com/reference/foundation/nsoperationqueue/1417849-cancelalloperations?language=objc) on the queue.

@futuretap - I don’t think that the warnings triggered by this second beta are easily resolved because it is not recognizing clearly sendable objects as such (e.g., an immutable `URLRequest`...

BTW, @futuretap, the main branch generates the same sort of compiler warning. It is not an issue limited to this PR and Xcode 13.3 Beta 2.

@brentleyjones - Thanks for the link to that folder. I wish that were in the documentation somewhere! I was tracking down some other problem that was clearly a result of...

To give credit where credit is due, it was "Programmer" who brought this to my attention. :)

I suspect he's borrowing this notion from the "reader-writer" pattern. The concept is that reads are done concurrently with respect to other read operations on this concurrent queue, but writes...

In my case at least, the main contention issues that I have involve updates on one thread or another, in which case reader-writer offers no advantage. I wasn't trying to...