Compute changeset in the background

[PhilippeWeidmann]

Checklist

• Reviewed the README and documents.
• Searched existing issues for ensure not duplicated.

Expected Behavior

We have to compute a large difference set ~50k elements, to do this we create a StagedChangeset in a background queue to avoid freezing the main thread. Is it okay to do it like this ? (We didn't encounter any issue but we were wondering is it was correct)
Now our issue is that the diffing process in a background queue is using too much memory. We placed an autoreleasepool around the check block in isContentEqual and this resolves the issue but we were wondering if maybe it wasn't something that you would potentially fix on your side ?

Environment

• Library version: 1.1.5

• Swift version: 5.3

• iOS version: 14.5

• Xcode version: 12.5

• Devices/Simulators: iPhone 12