-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
Speculatively implement LWG-3664 #2522
Conversation
to fix a regression when calling `ranges::distance` with array arguments which _should_ decay to pointers.
I'm mirroring this to the MSVC-internal repo - please notify me if any further changes are pushed. |
Merge `distance(i, s)` overloads to use `if constexpr` dispatch instead of concept overloading.
I pushed one more commit to directly use |
Thanks @timsong-cpp for paying enough attention to catch my bug on a weekend. For posterity: I bypassed branch policy to merge this with only one maintainer review due to time crunch. We did have some contributor reviews to add confidence. |
to fix a regression when calling
ranges::distance
with array arguments which should decay to pointers.If you look at LWG-3664 soon, you'll notice this doesn't match the proposed resolution. That original P/R is insufficient (Outlook Code™). Yes, that's right, the fix I suggested for the regression resulting from the fix I made in LWG-3392 is broken. :thonk: I've sent an updated PR with this change to LWG Chair, it will be a few days before the issue gets updated.