|
-
Sep 5th, 2022, 04:47 PM
#5
Re: [RESOLVED] Why No = Operator for ISomething and ISomething
No, that wasn't where I was coming from. What arose was that I had some classes that didn't have interfaces, but which I realized I needed to extract interfaces for. I had already implemented IEquatable (of C), and was using it in some fairly ancient code where I compared listItem(x) = otherListItem(x). When those were both lists of C, that worked fine. Once those became lists of IC, then that line broke.
Solving that is, as you said, quite simple, since listItem(x).Equals(otherListItem(x)) does the job, but that change had to be made, simple though it was.
My usual boring signature: Nothing
 
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
Click Here to Expand Forum to Full Width
|