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.

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

[operators] offers nice shorthand that should be exploited everywhere #2625

Closed
jensmaurer opened this issue Dec 30, 2018 · 3 comments
Closed

Comments

@jensmaurer
Copy link
Member

e.g. in [pairs.spec], [tuple.rel], [string.cmp], [string.view.comparison], [util.smartptr.shared.cmp] etc.

Adding a cross-reference to [operators] (for example in the synopsis when we also refer to the relevant subclause) would be helpful, probably.

@jensmaurer
Copy link
Member Author

jensmaurer commented Dec 31, 2018

Discussion on -lib reflector: [operators] provisions are used for chrono library. Requirements present in [operators] makes use for [pairs.spec] impossible. (It's unclear why those requirements exist in the first place.) Use of specific types in [operators] makes use for templates questionable.

Suggestion: Rephrase [operators] by not showing actual declarations, but referring to the == and != declarations present in the respective synopsis, and then giving the (syntax) rewrite rules. Remove the explicit requirements from [operators], but make sure to inherit the requirements from op== and op<. After that, remove redundant specification from the places listed above.

@jensmaurer jensmaurer added the decision-required A decision of the editorial group (or the Project Editor) is required. label Dec 31, 2018
@jensmaurer
Copy link
Member Author

Editorial meeting: There is some library work in this area.

@jensmaurer jensmaurer removed the decision-required A decision of the editorial group (or the Project Editor) is required. label Jul 16, 2019
@jensmaurer
Copy link
Member Author

Section removed and mooted by P1614R2 (<=> for the library).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant