Reactivecocoa: Debug events

Created on 27 Apr 2016  路  3Comments  路  Source: ReactiveCocoa/ReactiveCocoa

RxSwift provides a quite handy mechanism for debugging events via the debug operator ( more info here). There is a resourceCount as well, that could be interesting, although I think it would force us to scatter some macros around the code base.

I am up for doing the debug(), but I would like your opinion on the resourceCount).

Thanks @scotteg for the reference!

enhancement

Most helpful comment

馃憤 for debug. In RAC2, this was called logAll. I think it's useful.

resourceCount doesn't seem as useful to me, and it adds quite a bit of complexity, so I'm 馃憥 on that.

All 3 comments

This debug operator can be extremely handy, sometimes I do this manually to figure out what's going on which is not ideal to be honest.

Big 馃憤 to add this operator.

About resourceCount I think it can be helpful, probably using protocol extensions to introduce this behaviour in a meaningful way and internally use a swift flag to enable/disable this tracing. @jckarter has pointed here that empty functions may be optimized away by the compiler.

馃憤 for debug. In RAC2, this was called logAll. I think it's useful.

resourceCount doesn't seem as useful to me, and it adds quite a bit of complexity, so I'm 馃憥 on that.

Was this page helpful?
0 / 5 - 0 ratings