Static Analysis Tool

[Jon Alzate]

Hi,

I’ve been working on a static analysis tool tailored for event-driven architectures like RxJava. It uses event-sensitive analysis to detect complex bugs that traditional tools often miss, including race conditions, resource leaks, and incorrect handler behavior across asynchronous chains.

I’d really appreciate your thoughts on this:

- Are there specific RxJava issues or anti-patterns you’d like a tool like this to catch?

I realize RxJava is seeing reduced adoption, but this tool integrates well with its model, so I'm exploring where it can value.

Thanks for your time and any insights you can share.

Best,
John Allan

[Dávid Karnok]

Hi Jon,

Sorry for the late reply.

Indeed the adoption of RxJava is dwindling, plus it's been over 10 years since its conception, thus there aren't many anti-patterns I can remember being not addressed in some guides.

One recurring mistake was on Android when reacting to text field changes. Android uses mutable CharSequence for those fields so processing them in a background thread can result in all sorts of weird problems.

A second common problem is mostly due to Kotlin's encouragement of using curly braces for lambdas. We have SAM types such as Publisher and ObservableSource. Whenever an operator requires these types as parameters, developers use { } instead of () so they create a broken instance of these interfaces.

 

--
You received this message because you are subscribed to the Google Groups "RxJava" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rxjava+un...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/rxjava/13b7fbcb-4b25-4d68-b04d-7eb4153273aen%40googlegroups.com.

--

Best regards,

David Karnok