From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | David Fetter <david(at)fetter(dot)org> |
Cc: | PostgreSQL Development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Copypasta in the PostgreSQL source |
Date: | 2018-12-17 22:31:22 |
Message-ID: | 24806.1545085882@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
David Fetter <david(at)fetter(dot)org> writes:
> Please find attached a run of a tool that looks for duplicated tokens.
> I've removed some things that seem like false positives, basically all
> from the stemmer part of the source, but there's still a lot.
I thought you were talking about problems like "that that" typos,
but on looking at the file, what this is actually complaining
about is any duplicated code segments anywhere. I do not find
this helpful. Refactoring to the point that dozen-line code
stanzas never appear more than once would be incredibly invasive,
likely very bad for performance, and I don't think it'd improve
readability either.
> - Would it make sense to make some kind of git commit trigger that at
> least warns when a new one has been introduced?
Commit triggers are NOT the place for heuristics about code quality,
even if they're well-considered heuristics.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Alvaro Herrera | 2018-12-17 22:35:23 | Re: Copypasta in the PostgreSQL source |
Previous Message | Tomas Vondra | 2018-12-17 22:28:06 | Re: PATCH: logical_work_mem and logical streaming of large in-progress transactions |