Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I have a class with two events, call them StatusChanged and ValueChanged. I’m wondering about exposing these ‘streams’ as IObservable. Is implementing IObservable<Status> and IObservable<Value> on the same class ‘bad’? Is it likely to cause me (or users of my class) grief?
Implementing a covariant interface for different types is a really bad idea. Consider what happens if you cast the class to
IObservable<object>, which is now ambiguous.I’d rather have two properties
IObservable<Status> StatusObservable{get{...}}andIObservable<Value> ValueObservable{get{...}}. Simple, clean and it mirrors the two events your class offers.