From: | Peter Geoghegan <pg(at)bowt(dot)ie> |
---|---|
To: | Aleksander Alekseev <aleksander(at)timescale(dot)com> |
Cc: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Subject: | Re: Adding a clang-format file |
Date: | 2022-09-28 00:43:14 |
Message-ID: | CAH2-WzmHmW8=UcX8er=SMFcKFHFqXLBKi1PyZU9O_9RLwuXwOg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Tue, Sep 27, 2022 at 5:35 AM Aleksander Alekseev
<aleksander(at)timescale(dot)com> wrote:
> Personally I don't have anything against the idea. TimescaleDB uses
> clang-format to mimic pgindent and it works quite well. One problem
> worth mentioning though is that the clang-format file is dependent on
> the particular version of clang-format.
I was hoping that something generic could work here. Something that we
could provide that didn't claim to be authoritative, that has a
reasonable degree of compatibility that allows most people to use the
file without much fuss. Kind of like our .editorconfig file. That
might not be a realistic goal, though, since the clang-format settings
are all quite complicated.
--
Peter Geoghegan
From | Date | Subject | |
---|---|---|---|
Next Message | Michael Paquier | 2022-09-28 01:09:39 | Re: Refactor backup related code (was: Is it correct to say, "invalid data in file \"%s\"", BACKUP_LABEL_FILE in do_pg_backup_stop?) |
Previous Message | Peter Smith | 2022-09-28 00:13:22 | Re: GUC values - recommended way to declare the C variables? |