David Barbour
If you want first-class behaviors or behavior transformers, those will need a different abstraction than 'nested' behaviors. Nested != First Class. You'd have special functions to lift a first-class behavior as an argument (e.g. add a phantom type to prohibit non-causal observation), and to lower it into the main system for sampling (e.g. ArrowApply).
The usual model for arrowized FRP is based on this type: newtype Auto a b = Auto (a -> (b, Auto a b)) I would be very interested in how you would write an ArrowApply instance for such a type. So far my conclusion is: It's impossible. Do you have a different AFRP model in mind? Greets, Ertugrul -- nightmare = unsafePerformIO (getWrongWife >>= sex) http://ertes.de/