Closed jakhog closed 4 years ago
Would it make sense to throw ArgumentNullException
for all input parameters being Null on any method in these types of lists? That would make it very consistent.
Not sure I quite understand. Do you mean the methods like Contains
,Remove
, etc. ?
I was thinking about all methods taking an item as a parameter. Not sure it makes sense, but at least it would be very consistent - if you try to pass null
to it in any way it would throw an exception.
Hmm, it would make sense both ways - just different sense. The current implementation is permissive, so you could pass it along to other code reading it without worrying too much about exceptions. But that might not be necessary.
Introducing some mutable and immutable null free lists that we will use a few times in Runtime.
┆Issue is synchronized with this Asana task