Reputation
Top tag
Next privilege 125 Rep.
Vote down
Badges
3
Newest
 Supporter
Impact
~223 people reached

  • 0 posts edited
  • 0 helpful flags
  • 8 votes cast
Oct
29
comment Should I use a list or an array?
Doesn't LINQ level the field by adding a lot of that functionality for any IEnumerable (including an array)? Is there anything left in modern C# (4+) that you can only do with a List<T> and not an array?
Oct
3
awarded  Supporter
Oct
3
accepted Should I denote that a method satisfies an interface?
Oct
3
comment Should I denote that a method satisfies an interface?
@Graham but your comment will at least explain why the method was added in the first place, allowing a later editor to tell what the original intent was and make a better judgement as to whether or not it can be removed.
Oct
3
comment Should I denote that a method satisfies an interface?
Thanks. The IComparable example was just to identify exactly what I was talking about, in reality my concern was for more obscure interfaces that only exist within our project and whose methods might not be obvious
Oct
2
comment Should I denote that a method satisfies an interface?
@Telastyn do you have an alternative approach?
Oct
2
awarded  Scholar
Oct
2
comment Should I denote that a method satisfies an interface?
As of Visual Studio 2010, doing so doesn't add a region (it apparently just adds the required methods to the bottom of the class), but I still like the approach.
Oct
2
awarded  Student
Oct
2
asked Should I denote that a method satisfies an interface?