Comments on: ReSharper, day 20: Fix errors and warnings with Alt+Enter http://blog.excastle.com/2007/02/20/resharper-day-20-fix-errors-and-warnings-with-altenter/ Life, .NET, and Cats Sun, 12 Oct 2008 07:16:29 +0000 http://wordpress.org/?v=2.5 By: Joe White’s Blog » Blog Archive » TechEd 2008 notes: Busy .NET Developer’s Guide to F# http://blog.excastle.com/2007/02/20/resharper-day-20-fix-errors-and-warnings-with-altenter/#comment-21132 Joe White’s Blog » Blog Archive » TechEd 2008 notes: Busy .NET Developer’s Guide to F# Tue, 10 Jun 2008 02:13:03 +0000 http://blog.excastle.com/2007/02/20/resharper-day-20-fix-errors-and-warnings-with-altenter/#comment-21132 [...] it you’re done. (So what do you do if you use ReSharper and Alt+Enter already does lots of cool stuff? I wonder if keybindings in the editor are [...] […] it you’re done. (So what do you do if you use ReSharper and Alt+Enter already does lots of cool stuff? I wonder if keybindings in the editor are […]

]]> By: Joe White http://blog.excastle.com/2007/02/20/resharper-day-20-fix-errors-and-warnings-with-altenter/#comment-5614 Joe White Fri, 23 Feb 2007 10:55:00 +0000 http://blog.excastle.com/2007/02/20/resharper-day-20-fix-errors-and-warnings-with-altenter/#comment-5614 Ilya: That's why you don't /automatically/ fix warnings. If I use that pattern, it's up to me to decide whether to apply the quick-fix. I already get some false positives from ReSharper, for an unused event in a null object, and I just need to know not to fix them. <br> <br>And if it's safe to analyze parameters for protected methods, then why doesn't ReSharper do it? Ilya: That’s why you don’t /automatically/ fix warnings. If I use that pattern, it’s up to me to decide whether to apply the quick-fix. I already get some false positives from ReSharper, for an unused event in a null object, and I just need to know not to fix them.

And if it’s safe to analyze parameters for protected methods, then why doesn’t ReSharper do it?

]]> By: Joshua Flanagan http://blog.excastle.com/2007/02/20/resharper-day-20-fix-errors-and-warnings-with-altenter/#comment-5613 Joshua Flanagan Thu, 22 Feb 2007 21:19:00 +0000 http://blog.excastle.com/2007/02/20/resharper-day-20-fix-errors-and-warnings-with-altenter/#comment-5613 I think another quick fix for "Field is read but never written" should be "Initialize to default value" (reference types get null, ints get 0, bools get false, etc). I suppose I should tell JetBrains.... I think another quick fix for "Field is read but never written" should be "Initialize to default value" (reference types get null, ints get 0, bools get false, etc). I suppose I should tell JetBrains….

]]> By: Ilya Ryzhenkov http://blog.excastle.com/2007/02/20/resharper-day-20-fix-errors-and-warnings-with-altenter/#comment-5612 Ilya Ryzhenkov Wed, 21 Feb 2007 09:41:00 +0000 http://blog.excastle.com/2007/02/20/resharper-day-20-fix-errors-and-warnings-with-altenter/#comment-5612 The reason of not warning about unused parameter in public members (and some other analysis) is that such public member can quasi-implement interface in derived type: <br> <br>public interface IFoo { void foo(int p); } <br>public class FooBase { void foo(int pUnused){...}; } <br>public class Foo : FooBase, IFoo{} <br> <br>In the FooBase we can't remove pUnused because it will break Foo. Not only it is very time consuming to find all such cases, but it can break some external code, which is not under ReSharper control. It is, however, safe to analyse this for private, protected and internal members. <br> The reason of not warning about unused parameter in public members (and some other analysis) is that such public member can quasi-implement interface in derived type:

public interface IFoo { void foo(int p); }

public class FooBase { void foo(int pUnused){…}; }

public class Foo : FooBase, IFoo{}

In the FooBase we can’t remove pUnused because it will break Foo. Not only it is very time consuming to find all such cases, but it can break some external code, which is not under ReSharper control. It is, however, safe to analyse this for private, protected and internal members.

]]>