n.podbielski wrote:
Am I allone on that?
Yes/no. With a large framework, there's bound to be some inconsistencies. Yes, it would help if we could deduce the name of the method we want to call, based on fixed patterns. No, I don't see it happening. As for the range, I'd expect two ints, as the indexes are a good way to define a range. That's a bit harder to do with an IEnumerable. RemoveWhere(thisconditionistrue) or RemoveAll(thisconditionistrue); yes, your version sounds better, but it'll be hard to convince MS to change it. Especially after it's being used already in a lot of sourcecode.
Bastard Programmer from Hell :suss: if you can't read my code, try converting it here[^]
