combine-code-review

To find memory leaks in Swift Combine code, review your `AnyCancellable` handling and self-captures within `sink` closures. Identifying improper strong references prevents retain cycles and subsequent UI crashes in reactive chains.

Handling errors in Combine requires validating that publisher chains remain alive by replacing failing streams or using correct error propagation. Reviewing error handling ensures graceful failure recovery instead of crashing the subscription pipeline.

The correct way to use Combine operators like `flatMap` and `switchToLatest` involves validating your reactive logic against standard best practices. Checking operator usage prevents unintended concurrent publisher behaviors and data inconsistencies.

You can review Swift Combine code to validate subscription management and error propagation by targeting publishers, subjects, and cancellables. This ensures robust and efficient reactive code before merging new feature branches.

A Combine `sink` closure causes a retain cycle when it strongly captures self while holding an active `AnyCancellable` reference. Detecting these improper captures breaks the memory leak and stops unexpected UI crashes.

You need to check reactive Swift code for operator misuse when implementing complex pipelines with publishers and subjects. Validating operator usage before merging a feature branch catches incorrect stream manipulations early.