funcool

A channel for discussing and asking questions about Funcool libraries https://github.com/funcool/
mccraigmccraig 2016-06-08T08:35:31.000017Z

got an interesting question relating to alet @niwinz @dialelo - #C073DKH9P is looking to improve its subscriptions, which are basically sugar over #C0620C0C8 reactions... as far as i can see composing reactions could be done very neatly with alet

mccraigmccraig 2016-06-08T08:37:20.000018Z

this would make tracing difficult though - -fmap and -fapply would create new reactions with anonymous functions - i'm wondering if there is some way of passing alet binding information down to -fmap and -fapply so that the implementation could name the functions used in the reactions sensibly and make tracing easier

mccraigmccraig 2016-06-08T08:37:47.000019Z

(background here https://github.com/Day8/re-frame/issues/170 )

niwinz 2016-06-08T08:49:44.000022Z

IMHO, I'm not clearly understand how that are related 😞

niwinz 2016-06-08T08:50:15.000023Z

re-frame is too much complex for understand for me

niwinz 2016-06-08T08:56:01.000024Z

fmap fapply is a generic approach, and I think that if reframe needs something similar but more specialized, it should learn from generic implementation and implement a specific one.

mccraigmccraig 2016-06-08T09:06:22.000025Z

it's really only about tracing - in this case the fmap and fapply implementations will produce anonymous functions - if we could name those functions according to the alet binding steps/batches they relate to then tracing would be much better