为什么`changes`返回'Event t（Future a）`

问题描述

限时删除！！

code> type，这样它们才能被访问，直到 reactimate'阶段。

编辑：Tobias已经画出了一张插图：

The changes function has type Frameworks t => Behavior t a -> Moment t (Event t (Future a)). Future is abstract and there is only one function that consumes it (reactimate').

However, I can easily write the following function:

changes' :: Frameworks t => Behavior t a -> Moment t (Event t a)
changes' b = fmap (fmap const b <@>) (changes b)

to get a normal (non-Future) event.

Is something wrong with that function? If not, why does the original changes function have a more restrictive type?

解决方案

The function changes returns different values than the function changes' that you describe. The key point is the following:

Consider a Behavior defined by stepper (or accumB), which happens to change at time t0. What value does the Behavior have at this moment in time? The answer is that the Behavior takes on the new value for all times that are strictly larger than the time of change, t > t0, and that it still has its old value at time t0. In other words, the changes' function returns an event whose values are the old values of the Behavior at the time of change. In contrast, the changes function returns the new ("future") values. For various reasons that have to do with recursion, the new values are wrapped in a Future type, so that they cannot be accessed until the reactimate' phase.

EDIT: Tobias has drawn a picture for illustration:

这篇关于为什么`changes`返回'Event t（Future a）`的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持！

1403页，肝出来的..