Clojurians Log v2

> What should I read to deepen the understanding of that? This might give you some thoughts - https://day8.github.io/re-frame/flows-advanced-topics/#reactive-context

Thanks @kimo741!

It's not heresy, and that's exactly what reg-sub-raw is for. But if it can be a signal function, it should be a signal function, yes.

Thanks a lot! What should I read to deepen the understanding of that? Or could you, pretty please, provide explanation for that?

I'd just refer you to the impl. :) It's very, very small.

ok, cool!

Here's a documented example of using subscribe within a reg-sub-raw handler: https://day8.github.io/re-frame/flow-mechanics/#reg-sub-raw

If I get it right, reg-sub-raw will not be cached or treated as a pure function, right? So using @(rf/subscribe [:smth]) inside a regular subscription is a bad move, because a regular subscription node is treated as a cacheable pure function.

The requirement for sub handlers to be pure functions is purely a design one. It makes things more predictable and easier to test. Of course, you should definitely avoid side-effecting subscription handlers or handlers that rely on mutable data structures that re-frame knows nothing about. But it's much less important to make them not rely on other subscriptions, since they're all a part of the same mechanism. Regarding the cache - subscribe does the caching, not any reg-... function. A regular subscription, i.e. one created with reg-sub, is nothing but a wrapper around what reg-sub-raw does. That wrapper deals with signals and tracing, and creates that needed reaction for you, that's about it.

Thanks a lot, Eugene!