Greg Parker

@gparker I don't know what this means, but I'm scared now

@rentzsch @gparker Expect immutable types to behave like immutable types …

@danielpunkass @rentzsch @gparker The question boils down to what is "value-like" and who defines that interpretation? UIImage? NSData?

@Bagelturf @danielpunkass @rentzsch @gparker anything you'd call -isEqual: on

@ben_lings @Bagelturf @rentzsch @gparker Is that meant to be a joke?

@danielpunkass @Bagelturf @rentzsch @gparker for non-value objects, you'd probably just use pointer equality

@ben_lings @Bagelturf @rentzsch I suspect @gparker’s warning applies to a far smaller set of classes than anything you’d call isEqual: with.

@gparker do you mean don't objc_setAssociatedObject(<value_type>, key, obj) or don't objc_setAssociatedObject(obj, key, <value_type>)?

@nicklockwood @gparker More like don’t use associated objects for NSString or UIColor.

@steipete @gparker you clarified the wrong bit ;) Does problem arise from using them as the target, or the value being associated (or both)?

@nicklockwood @steipete @gparker surely means the former, the second wouldn't be a problem with instance deduping.

@gparker que?

@gparker I’ve been bit hard by NSIndexPath there. Now I convert to strings first.

@SlaunchaMan How are you storing the strings, then? Or are you just using the strings for comparisons later?