@DarkPlayer@lemmy.world to Programming@programming.dev • 2 months agoHow far should a programming language aware diff go?semanticdiff.comexternal-linkmessage-square22fedilinkarrow-up177arrow-down14
arrow-up173arrow-down1external-linkHow far should a programming language aware diff go?semanticdiff.com@DarkPlayer@lemmy.world to Programming@programming.dev • 2 months agomessage-square22fedilink
minus-squaremoxlink10•edit-22 months agoThat’s not a blind spot in my comment. See my final paragraph. It’s only one sentence. Maybe it was easy to miss. :)
minus-square@Solemn@lemmy.dbzer0.comlinkfedilinkEnglish1•2 months agoI like the idea, but I can’t come up with any method that won’t devolve into most reviewers only checking the highlighted parts tbh.
minus-square@Bogasse@lemmy.mllinkfedilink1•2 months agoOh yeah, so I’m that other kind of guy 🥺 I kinda like your idea, but I think it can be difficult to detect some confusing situations. I think it would be a better idea, but I don’t think it’s a full replacement.
That’s not a blind spot in my comment. See my final paragraph.
It’s only one sentence. Maybe it was easy to miss. :)
I like the idea, but I can’t come up with any method that won’t devolve into most reviewers only checking the highlighted parts tbh.
Oh yeah, so I’m that other kind of guy 🥺
I kinda like your idea, but I think it can be difficult to detect some confusing situations. I think it would be a better idea, but I don’t think it’s a full replacement.