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

[2023-06 CWG Motion 4] P2361R6 Unevaluated strings #6279

Closed
jensmaurer opened this issue Jun 17, 2023 · 2 comments · Fixed by #6318
Closed

[2023-06 CWG Motion 4] P2361R6 Unevaluated strings #6279

jensmaurer opened this issue Jun 17, 2023 · 2 comments · Fixed by #6318
Assignees
Milestone

Comments

@jensmaurer
Copy link
Member

jensmaurer commented Jun 17, 2023

https://www.open-std.org/jtc1/sc22/wg21/docs/papers/2023/p2361r6.pdf

@jensmaurer jensmaurer added this to the post-2023-06 milestone Jun 17, 2023
@jensmaurer jensmaurer self-assigned this Jun 17, 2023
@tkoeppe
Copy link
Contributor

tkoeppe commented Jun 17, 2023

Mail from @cor3ntin:

in dcl.pre/p10, there is a minor conflict between P2361 and the current draft.
However, P2741R3 also on the ballot, assumes P2361 is going to get approved,
so i would recommend

  • Merging P2741R3 before P2361
  • When applying P2361, do not apply the changes in dcl.pre/p10 and dcl.pre/p1, as P2741R3 contains these changes already.

@tkoeppe
Copy link
Contributor

tkoeppe commented Jun 17, 2023

Hm, merging motions out of order is a bit unusual. @jensmaurer Let me know if you need any advice on this, otherwise I'll leave you to figure something out (but do say in the commit message how this is being reconciled).

@cor3ntin Could you please point out the prior change that causes the merge conflict between your paper and the current draft? (I'd like to mention that in the reconciliation message, too.)

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

Successfully merging a pull request may close this issue.

2 participants