Browse Source
This may destroy code - see "DoesNotSuggestMovingIntoBodyAfterMethodCall". This issue requires some extra logic. I doubt that the issue is useful any longer when that logic is implemented. Safely moved can only be constant expressions (which should be handled by the compiler anyway). It needs to check that it doesn't move non constant code beyond any method/property usage or field assignments - there are no much use cases left for that action.pull/45/merge
1 changed files with 4 additions and 4 deletions
Loading…
Reference in new issue