As far as I know, it is recommended to favor composition (io.reactivex.Single#compose) instead of custom operators (io.reactivex.Single#lift).
As the Javadoc of lift suggests, there are some optimizations that a custom operator must implement itself, that built-in operators implement already.
Besides, if I remember correctly, this is what @jponge recommends for Mutiny extensions as well (start with composition and use custom operators as a last resort).
I would imagine the same feature (HttpResponse expectations) will be implemented with composition in Mutiny, it would be nice to be consistent.
As far as I know, it is recommended to favor composition (io.reactivex.Single#compose) instead of custom operators (io.reactivex.Single#lift).
As the Javadoc of lift suggests, there are some optimizations that a custom operator must implement itself, that built-in operators implement already.
Besides, if I remember correctly, this is what @jponge recommends for Mutiny extensions as well (start with composition and use custom operators as a last resort).
I would imagine the same feature (HttpResponse expectations) will be implemented with composition in Mutiny, it would be nice to be consistent.