Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[algorithms] Inconsistency for parameter x vs parameter named x #4086

Open
JohelEGP opened this issue Jul 21, 2020 · 3 comments
Open

[algorithms] Inconsistency for parameter x vs parameter named x #4086

JohelEGP opened this issue Jul 21, 2020 · 3 comments

Comments

@JohelEGP
Copy link
Contributor

It seems that the former is prevalent.
@jensmaurer jensmaurer added the decision-required A decision of the editorial group (or the Project Editor) is required. label Jul 21, 2020
@jensmaurer jensmaurer removed the decision-required A decision of the editorial group (or the Project Editor) is required. label Nov 7, 2023
@jensmaurer
Copy link
Member

Editorial meeting 2023-11-06: We want to say "no parameter named X", to highlight that the name isn't really relevant for C++; naming the parameter is just a method of specification.

Pull request welcome.

@JohelEGP
Copy link
Contributor Author

JohelEGP commented Nov 7, 2023

I have reviewed the use of "parameter" in [algorithms] to remind myself what this issue is about.
It seems that the editorial meeting consensus is with regards to template parameter names such as BinaryPredicate.
I think those are perfectly covered by [algorithms.requirements].
My target are function parameter names.
Sorry for not being clear enough.
Here is an example of the inconsistency.

draft/source/algorithms.tex

Lines 4288 to 4291 in dc6eed0

Let \tcode{last2} be \tcode{first2 + (last1 - first1)}
for the overloads with no parameter named \tcode{last2},
and let \tcode{pred} be \tcode{equal_to\{\}}
for the overloads with no parameter \tcode{pred}.

@jensmaurer
Copy link
Member

No, we did discuss exactly the function parameter naming issue that your example is about.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@JohelEGP @jensmaurer