MyDeveloperDay added a comment. Just an observation, I have this in my Day Job all the time..
1. Developer A develops a piece of code 2. Over the years the developers in our group learn that code and become familiar with it 3. Developer B arrives in our group, telling us we are doing it all wrong we don't understand, but they are going to refactor it for us and correct the error of our ways. 4. Now now one in our group understands the code, except Developer B 5. Developer B gets annoyed at our lack of understanding of his/her more masterful refactoring skills and disappears... 6. No one understands the code and everyone has to relearn the code. (Developer B's name is now mud!) Refactoring is an important step, but in my view it shouldn't be the first contribution someone makes. I understand it you think its better, it possibly is.. but those of us who have been in here for years now no longer recognize the code and have to read it with a fine tooth combe again. I personally don't see the code as being functional equal before or after, and I've kicked myself for not being more thorough in review when someone does this..that's probably my lack of understanding. If you are fixing a bug, then ok, lets look at it, but just because you don't like the way it looks or you think there is repetition. If your an experienced contributor then maybe you'd have our trust...but otherwise we need to express caution here in my view. Just incase you chose to up and disappear. Refactoring yes, but if its "Drive by" Refactoring, I'm not so keen. Repository: rG LLVM Github Monorepo CHANGES SINCE LAST ACTION https://reviews.llvm.org/D121757/new/ https://reviews.llvm.org/D121757 _______________________________________________ cfe-commits mailing list cfe-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
