I wrote up a long description of this yesterday and your forums deleted it all - so I'm going to be very terse today and hope you make the effort to reproduce it anyway - since it's trivially easy to make go wrong.
If I use refactor to transform memberfun1 to become: bool memberfun1(int defaulted_arg = VALUE);
Then memberfun 2 and 3 are trashed as follows: bool foo::memberfun2() { return memberfun1(); } bool foo::memberfun3() { return memberfun1() : ; }
Very bad bug - easy to miss as memberfun2 still compiles --- only by careful inspection of the code (or later bug reports from testing) will you ever know that it did something truly awful). :(
A part of me wonders if this was a consequence of the out-of-order syntax highlighting issue (like the edits to the code were being interfered with by VS2013).
I haven't had a chance to directly test this yet.
UPDATE:
This is definitely a bug - not related to my previous issue with load order of VA/Update1.
Tons of stuff becomes wrecked if I try to use change-signature right now
Yes, I was able to reproduce the problem both with your example from the first and from the second post. A developer is already working on this.
Sorry for the inconvenience, again. I'm glad you reported this, and am looking forward to your experience with the fix, once it becomes available. We will update this thread, so if you click on the "Subscribe to this topic" link, you should get an email notification about the release of this bug fix.
Very bad bug in refactor
Posted - Jan 28 2014 : 3:02:57 PM
