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
[range.cartesian.view] Fix neglect for parent_ #5770
Conversation
@jwakely Does this require an LWG issue? |
If this is the LWG, there is no way to implement a functional |
That may well be so, but is not an editorial concern.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Use semantic line breaks:
https://github.com/cplusplus/draft/wiki/Specification-Style-Guidelines#latex-source-code-formatting
That's fine. This is not a final standard, there is no great urgency to fix defects in a draft. Implementors can easily do this without waiting for an LWG decision. It's common that we implement fixes before they make it into the draft. Although the changes here seem correct, I don't think it's editorial. Please submit an LWG issue instead, thanks! |
Co-authored-by: Jonathan Wakely <github@kayari.org>
Co-authored-by: Jonathan Wakely <github@kayari.org>
Could you kindly edit the pull request to avoid sounding disparaging of the existing work and the people who have contributed it? |
@tkoeppe Sorry for the misunderstanding caused by the misuse of words, I will be more careful with words in the future pull. @jwakely, thanks for the suggestion. If this is definitely an LWG, I'd like to ask when it would be appropriate to submit it to the LWG, as the C++23 draft hasn't been published yet. |
Much appreciated! The paper doesn't ultimately "belong" to the author, so even if an author later changes their mind or clarifies something, that cannot just "bypass" the committee approval. So the normal thing to do in that case is to record the desired correction in an LWG issue. Usually those kinds of issues can be processed very fast. In any case the final standard won't be released for many months, and the committee can always approve issues. So there's plenty of time. It's perfectly normal for large papers to contain errors and have those fixed later on. |
Specifically addressing your question, you should submit an issue to lwgchair now, so that the matter does not get lost. |
Closed and intends to submit LWG for this. |
This seems editorial bug in the paper.