Structural comparison vs. performance of oneWayLazy about elmish.wpf

[cmeeren]

A very simple workaround/method (on the library side) is to add an isEqual : 'a -> 'a -> bool parameter to Binding.oneWayLazy, allowing users to optimize as needed. It could be as simple as (=) (which is the current behavior), but it could also be e.g.

fun (simple1, list1) (simple2, list2) ->
  simple1 = simple2 && Object.ReferenceEquals(list1, list2)

This should of course be documented to provide clear guidance.

I kinda like this. I don't like pushing too much on users, but after all, oneWayLazy is there solely for performance reasons, and currently it is potentially lacking in that respect.

[inosik]

The React renderer for Fable has similar functions: lazyView and lazyViewWith, with lazyView being the same as lazyViewWith (=). Elmish.WPF could follow the same principle, so users can provide their own equality functions, if (=) turns out to be too slow.

[cmeeren]

Yes, I like that very much. Thanks! 👍

[cmeeren]

Closed by a5e1170