Ha! I just stumbled onto this recently to solve an ugly performance issue and it works great.
The cost is a layer of complexity added to the update function. In this way, the intermediate calculations need be done just once per update rather than spread out many times over the view. Well worth the effort to keep users oblivious to the difficulties and happy with the results. Perhaps there is a way to store such dependent state separately? Until then I shall keep this technique close to hand. On Tuesday, July 25, 2017 at 3:11:22 AM UTC-4, Peter Damoc wrote: > > Keep derived data in the model if it makes sense to keep derived data in > the model. > . . . > There is NO FATE, we are the creators. > blog: http://damoc.ro/ > -- 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 elm-discuss+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
