use_memo should warn/throw if passed anything but an array for dependencies

[mattrunyon]

Related to #354 where we accidentally had a dictionary instead of an array for the dependencies of use_memo. We should at least warn (maybe throw) that memoization will not happen properly if a non-array is passed

I also don't think the dependencies typehint is right. set[Any] | Sequence[Any]. Sets are unordered, so you could cache miss just based on set iteration order. Sequences contain list, tuple, and range. Range doesn't really make sense IMO. List vs tuple I could see either being valid. From what I can find, tuples are immutable and a little bit more performant than lists

[mofojed]

@mattrunyon it wasn't a dict, it was a Set, which we allow as a type. @jnumainville maybe we shouldn't allow a Set though (as that bug in #354 is kind of subtle)

[mattrunyon]

Ya I just updated my comment here. It should just be List or maybe List | Tuple. Sequence includes other data types which we don't want. Set is unordered and definitely shouldn't be allowed considering the comparison is just based on position in the array

[mofojed]

After discussion, definitely should not be allowing sets - the order definitely matters, e.g.

@ui.component
def Foo():
  val1, setValue1 = use_state(0)
  val2, setValue2 = use_state(0)
  
  # These values are the same! Should be using an order so the slot they're in matters.
  new_val = use_memo(lambda:...., { val1, val2 })

[jnumainville]

ah, yeah, a set is too permissive and would be too much hassle to make work even if it didn't have the issue of dropping duplicate items