On Oct 5, 2016, at 5:22 AM, Noah Hall <[email protected]> wrote: > > It makes it hard to perform eq on.
This is the big one from my standpoint. To optimize lazy views (and memory/gc behavior), I've at times written "smart" update functions that check for equality with existing values before constructing new values. This then started blowing up with a runtime exception caused by comparing functions for equality. Now, I'm paranoid and both avoid functions in models and equality comparisons because someone else may not have exhibited one or the other of these forms of caution. It would be nice if Elm would treat functions that aren't obviously equal as unequal but I recognize that this could lead to compiler optimizations changing the behavior of programs which isn't great either. Mark -- You received this message because you are subscribed to the Google Groups "Elm Discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
