Ah yeah, as an example say you have a list of messages, a message being a record, if you add a new message to the 'end' of the list then every-single-message-list-cell will be recreated, although not the message records themselves, that is because Elm is functional and a List is a Cons List. If, however, you put the new message at the front (and render it backwards) then it changes none of the other.
Now for a list of todo's, if you touch one in the middle then all the list cells before it will be recreated, but the todo's themselves will not even in those. That is not really something to worry about much though to be honest. On Friday, November 4, 2016 at 2:17:36 PM UTC-6, Lars Jacobsson wrote: > > Yeah but that was kind of my point though. In an app where 'something' > (using your example) is the main piece of data, say a list of todos, then I > wouldn't want the whole slice thrown away on every update? Not too familiar > with the Elm core so I dont know where to look! -- 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.
