On Tuesday, June 6, 2017 at 3:20:42 PM UTC+1, Rupert Smith wrote: > > The problem with long running computations in a single threaded UI is that > they may cause the UI to block and become unresponsive for a period. > Definitely not an acceptable user experience. > > I have created a library for helping with AI-type searches. This provides > a 'next' function that steps the search along by examining a single 'node' > in the search space. The search space forms a graph, and as each node is > de-queued from the search buffer, it is checked to see if it is a goal > state, and all its successor states are created from a user supplied 'step' > function, and en-queued onto the search buffer. >
I should add, it seems likely any long-running process will be structured to have a loop at the top-level. This loop can be turned into a continuation '() -> More a', to break the task down into steps. So this does not just apply to my AI search library but any longer computation we might want to do that puts too much delay into the UI update cycle. -- 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.
