On Feb 1, 2020, at 9:00 AM, Manlio Perillo <manlio.peri...@gmail.com> wrote: > > On Saturday, February 1, 2020 at 12:45:23 AM UTC+1, David Riley wrote: >> Please don't do this. Or make it an opt-in. This is not a good change to >> force on users by default. >> > > You are right, thanks. > I guess the only possible solution is for gofmt to not align the fields, > using only one space character between field name and field type.
I don't know if that's the *only* solution; I think the current solution isn't terrible, even if it does lead to somewhat larger diffs when things are changed. The fact that it already only aligns them in a "clump" makes it a bit easier to segment those changes out. The status quo is not, IMO, terrible (though again it is just my opinion). Single space would definitely be preferable to single tab, since that's already fairly prevalent and reasonably legible. It ain't always pretty, but it gets the job done without a lot of weird jumping all over the place like tabs would invariably do. If computing had evolved differently to the point where there were actual canonical tab stops at, say, 4 and 50 columns instead of just every n columns, this would be a fine proposal. Alas, we have the ambiguous settings we have today. This is, perhaps, one opportunity Unicode has to remedy things, but relying too much on fancy Unicode features to render code that is generally understood to be "sort of flexible ASCII", as Go is, is also a minefield when it comes to compatibility with existing tools. - Dave -- 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/50460D06-D16E-46A5-A31D-B9CE52D247CD%40gmail.com.
