▲ 72 ▼ How far should a programming language aware diff go? (semanticdiff.com) submitted 2 years ago by DarkPlayer@lemmy.world to c/programming@programming.dev 23 comments fedilink hide all child comments
[–] FizzyOrange@programming.dev 1 point 2 years ago (1 child) Yeah but sometimes you do get meaningless changes that aren't just whitespace even with auto formatters. For example if you change the indentation on some code and that causes it to wrap an expression. permalink fedilink source parent hideshow 2 child comments replies: [–] SpaceNoodle@lemmy.world 1 point 2 years ago (1 child) How is that not whitespace? permalink fedilink source parent hideshow 2 child comments replies: [–] FizzyOrange@programming.dev 1 point 2 years ago git diff -w only ignores whitespace within a line (e.g. changing indentation). It doesn't ignore adding or removing new lines. But even if it did, wrapping a function call or a long string can introduce extra commas or quotes. permalink fedilink source parent
[–] SpaceNoodle@lemmy.world 1 point 2 years ago (1 child) How is that not whitespace? permalink fedilink source parent hideshow 2 child comments replies: [–] FizzyOrange@programming.dev 1 point 2 years ago git diff -w only ignores whitespace within a line (e.g. changing indentation). It doesn't ignore adding or removing new lines. But even if it did, wrapping a function call or a long string can introduce extra commas or quotes. permalink fedilink source parent
[–] FizzyOrange@programming.dev 1 point 2 years ago git diff -w only ignores whitespace within a line (e.g. changing indentation). It doesn't ignore adding or removing new lines. But even if it did, wrapping a function call or a long string can introduce extra commas or quotes. permalink fedilink source parent