
I think, “Reactive” would be much better. Most modules about reactivity are FRP libraries anyhow. If we would have “FRP” as a top-level name, where would the few non-functional reactive libraries fit into? As I said, I plan to move from “FRP” to “Reactive” for Grapefruit anyhow. All the best, Wolfgang Am Freitag, den 17.02.2017, 10:14 -0600 schrieb amindfv@gmail.com:
"FRP" seems like something we could make an allocated name.
Tom
El 17 feb 2017, a las 08:45, Wolfgang Jeltsch
escribió: Hi!
When uploading a new version of grapefruit-frp yesterday, I got the following warning from cabal-install:
Exposed modules use unallocated top-level names: FRP
This made me wonder which top-level names are actually “allocated”. I tried to find this out from the Cabal sources, but the GitHub search functionality revealed no occurrences of the word “unallocated”.
Regarding my concrete case, I think it would be good to change “FRP” to “Reactive”, which is what Reactive Banana is using, for example. However, is “Reactive” an “allocated” top-level name?
All the best, Wolfgang