(The question was rewritten after discussing with @AndreasOetjen below. Thanks for his comments.)
I ran into an issue with using UITableView
with diffable d
I'm a little confused about your last sentence: You write my item is an enum with associated values of reference type, but in your example above you use struct Book
, which is a value type. Regardless of that, the following has to be kept in mind for any case:
Hashing is all about "object" identity. It's just a kind of shortcut to improve identity comparisons, folding etc.
If you provide a custom hash implementation, two objects a
and b
must behave in a way that a == b
implies that also hash(a) == hash(b)
(The other way round is almost always also true, but there may be collisions - esp. with weak hash algorithms - when this is not the case).
So if you only hash the title
and author
, then you have to implement the comparison operator in a way that it also only compares title
and author
. Then, if notes
change, neither the data source nor any body will not detect identity changes at all.
UITableViewDiffableDataSource
is a means to facilitate the synchronization of insert/delete statements between view and data source. If you ever got this
*** Terminating app due to uncaught exception 'NSInternalInconsistencyException', reason: 'Invalid update: invalid number of sections. The number of sections contained in the table view after the update (3) must be equal to the number of sections contained in the table view before the update (3), plus or minus the number of sections inserted or deleted (0 inserted, 2 deleted).'
then a diffable data source is your friend.
I hope this helps a little.