Dnia 2020-02-18, o godz. 10:16:57 Manlio Perillo <manlio.peri...@gmail.com> napisał(a):
> Here is an example of a diff with a lot of noise, where the actual change > is very hard to see: > https://gist.github.com/perillo/c5b3bdff9e8db9c89f316670d129c0dd > > Note that using `git diff -w` is not a solution, since it can only be used > locally. The full diff will be shown by github and friends. Yes. It could be easily fixed with cosmetic changes to gofmt in a way that is tab-width neutral [1] but I doubt it would be seriously considered given current NIH-driven mood of dev's hive. [1] use marker relative to the opening brace hinting at the desired comment position, ie. compute type-start position relative to the opening brace then comment-start position relative to the marker from the comment of the brace line. Adjust both positions modulo 8 rounded up. Field name that gets over past the established type-start position stays over. Done. Everything, except overlong names, lines up on the screen with ts=2, ts=3, ts=4 as well as with ts=8. Changesets contain no whitespace changes, because there is no such gofmt introduced changes anymore — ofc unless you change type identifier past the rounded 8 boundary. Then whole struct will make to the changeset, not just huge parts of it. Hope this helps, > Manlio -- Wojciech S. Czarnecki << ^oo^ >> OHIR-RIPE -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/golang-nuts/20200219031558.77411fc7%40xmint.
