Yampa's API -- request for comments

[ivanperez-keera]

Yampa now has a mature codebase that is clean, with lots of tests. Although of course there's room for improvement, I'd like to shift focus a bit on trying to make sure that the API that Yampa offers is "appropriate", meaning that the types and functions exported, and the module hierarchy, form an elegant and clean design.

If you have any thoughts of what does or doesn't belong, what should be named different, what should be moved around, etc. please comment on this thread. The library hierarchy is also within scope here.

[vitalibarozzi]

Only indirectly related to Yampa, but I wonder if simple-affine-space should have Linear instances (like the example, for V2) or maybe in a different package extending it. I just remember having to do this many times in different places.

Regarding Yampa itself, I would love to see some examples in the functions documentation on Hackage. I guess not everything need examples; seems to me at least switches, but everything below the switches section in FRP.Yampa could benefit from it.

[ivanperez-keera]

It's always bugged me that I don't have a good name for the FRP.Yampa.EventS module. It somehow has a similar responsibility as FRP.Yampa.Hybrid.

Maybe they belong together, or maybe a different split is more appropriate. Any thoughts?

[ivanperez-keera]

On a similar note, I wonder if FRP.Yampa.Loop and FRP.Yampa.Scan belong together.

[ivanperez-keera]

I've never liked the name FRP.Yampa.Basic. Basic means nothing. It should have a better name, or maybe those primitives belong somewhere else.