I've got incoming data where a reader can connect ...
# coroutines
r
I've got incoming data where a reader can connect (via bluetooth), where cards can be put on, where data can be read from. Currently, I have that modeled as nested `Flow`s, but the cancelation is currently a bit... suboptimal, and advancing to the next reader isn't as clean as I hoped it would be. Even using
collectLatest
isn't really working that well, I'm not sure how to declare an element invalid - or is
collectLatest
the correct way here? Or should I be using a different abstraction that
Flow
if a previous element becomes dead/invalid?