Rename [cmp.syn] to [compare.syn] #1991
Comments
|
On Mar 27, 2018, at 4:21 AM, Jens Maurer ***@***.***> wrote:
along the reasoning in #1958.
Sorry, but I respectfully disagree with that reasoning, both in this specific case and in general.
If a clause has a stable tag of the form [X], it seems entirely reasonable to me that each of its subclauses have a stable tag of the form [X.Y].
I am therefore not in favor of making even well-intentioned changes to this scheme. Instead, I would favor going the other way: finding any stable tags that do not adhere to the described scheme and making them conform to it.
But I also am sympathetic to the widely-held view that stable tags should be, well, stable unless there are truly compelling reasons for a change. Let's please not touch tags without significant need.
|
|
@W-E-Brown, thanks for your comment. I have added references to the respective pull requests #1960 and #1993. |
|
I'd like to point out that [cmp.syn] in particular was added as late as November 2017, so I view the "stable" argument carrying less weight. |
jensmaurer
added
the
decision-required
|
@W-E-Brown: The problem with this "nesting" approach is that it's brittle and unmaintainable. We have moved sections and synopses around in the past, or introduced "ill-fitting" headers like By contrast, header-name.syn seems to be reasonably easy to understand and maintain, and it's trivially as stable as the header name itself. |
|
We are not going to rename all existing stable labels to conform to the [header-name.syn] pattern, but [cmp.syn] is brand-new, so renaming that one is much lower-cost, and we're going to do that. |
|
See #1958 for more explanation. |
jensmaurer
removed
the
decision-required
along the reasoning in #1958.
The text was updated successfully, but these errors were encountered: