New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Remove RACAsyncSubject in favor of RACReplaySubject #87
Comments
Yeah I've wondered about this before... Note that I think the real value is the semantic difference between the two. I'd be interested in getting @xpaulbettsx's thoughts on this. |
So, the only difference between them that should be there is that |
@joshaber The typical use case for I think the problem is that
It's worth noting that interfaces typically shouldn't expose whether a |
Yeah good point 👍 |
FWIW, I'm going to do a pass through soon to do some housekeeping. I can remove |
🤘 Sounds good, though we should keep in mind that |
✨ 👍 |
It's not clear what advantage
RACAsyncSubject
offers overRACReplaySubject
. It seems like the latter has a strict superset of the former's behavior. It also seems like a safer default to replay the whole subscribable stream, rather than just the last thing sent.The text was updated successfully, but these errors were encountered: