[<<][meta_siso][>>][..]
Wed Jul 22 00:50:11 EDT 2015

Removing the 2 approaches comment

-- Representing programs that implement state space models as Arrows.
---------------------------------------------------------------------
--
-- Approach A
--
--  * A state space model update function (s,i) -> (s,o) is not an
--    Arrow: state accumulates s1 x s2 -> (s1,s2)
--
--  * However, a _generator_ of such an update model is an Arrow
--
-- Moral of the story: the representation problem can be solved by
-- shifting a level from thing to constructor of thing.
--
-- generator = language -> program
--
-- What does language look like?  Something that contains:
--   - unit delay
--   - pure functions
--   - spatial combinators (representations of map, (comm)fold, ..)
-- The rest is an instance of ArrayLoop

-- Approach B
--
--  * A stream operator is represented by an existential type
--
--    See Sys.hs for a complete example (FIXME: doesn't work any more
--    / probably never has.)




[Reply][About]
[<<][meta_siso][>>][..]