From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: guix-devel@gnu.org
Subject: Re: Regarding the vertical alignment in the record definitions
Date: Thu, 05 Dec 2024 16:13:00 +0900 [thread overview]
Message-ID: <87frn2li0z.fsf@gmail.com> (raw)
In-Reply-To: <87frn538q2.fsf@wolfsden.cz> (Tomas Volf's message of "Tue, 03 Dec 2024 01:34:29 +0100")
Hi Tomas,
Tomas Volf <~@wolfsden.cz> writes:
> Hello Guix,
>
> I would like to bring up for debate the convention the project has of
> vertically aligning the record definitions.
I don't think that's a project convention. It's more like it's a
convention of some individual in the projects :-). At least I don't
follow it, except sometimes when touching a piece of code already
indented that way.
> While some amount of noise in diffs is expected in any lisp language
> (the trailing `)'), the vertical aligning makes it worse. It (in my
> opinion) complicates both reviewing and re-basing (due to merge
> conflicts).
>
> For example, take this patch I sent today. It adds *a single field* to
> the record. However the patch (that someone needs to review and make
> sure is correct) looks like this:
I agree it's a bit tedious, both manually and also in diffs. My
personal preference is to leave just one space between the field name
and the value, that also holds for variable bounds in lets, etc., to
avoid the problem (at the cost of some visual clarity, I guess).
One day maybe we'll have a general tool like 'scheme-fmt' to run on a
file save hook that'd fix the format question for good, like Python has
with 'black' or 'ruff', etc. I have on mind to work on such a tool, but
it's low in the list.
--
Thanks,
Maxim
next prev parent reply other threads:[~2024-12-05 7:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-03 0:34 Regarding the vertical alignment in the record definitions Tomas Volf
2024-12-05 7:13 ` Maxim Cournoyer [this message]
2024-12-05 8:41 ` indieterminacy
2024-12-09 0:31 ` Maxim Cournoyer
2024-12-05 7:35 ` Efraim Flashner
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87frn2li0z.fsf@gmail.com \
--to=maxim.cournoyer@gmail.com \
--cc=guix-devel@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).