Enhance value assignment equality for IterableSignals

[leoafarias]

The current implementation of the equality check in the IterableSignal class (which ListSignal extends) compares the iterable references instead of comparing the actual values of the iterable.

This behavior is expected when assigning a list using signal, but in my opinion using listSignal, or some of the other IterableSignals, this should be handled.

final value1 = [1, 2, 3];
final value2 = [1, 2, 3];

final list = listSignal(value1);

effect(() {
  print('list changed');
  print(list.value);
});

list.value = value2;

// prints: list changed
// prints: [1,2,3]

Suggestions

1. Adapt our equality check within IterableSignal to align more with how collection functions are handled, thus ensuring a comparison based on the value.
2. Allow the provision of a specific equality function for each iterable signal function, enabling more flexible and customised evaluation.

[rodydavis]

Do you mean you want ListSignal to compare with DeepCollectionEquality?

[leoafarias]

Yes, but if you don't want to bring as a dependency, maybe we can create an equivalent. Let me know what makes sense, and I can give a try on a PR.

[rodydavis]

I'm trying to hold off adding dependencies as long as possible to maximize compatibility with projects.

I think having something equivalent would be a great addition!

[leoafarias]

I agree, will create a PR for you to review if it makes sense.

[rodydavis]

Sounds great!