-
Notifications
You must be signed in to change notification settings - Fork 5k
Fix regression caused by overload resolution. #115164
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
Fix regression caused by overload resolution. #115164
Conversation
Tagging subscribers to this area: @dotnet/area-system-buffers |
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.
Pull Request Overview
This pull request fixes a regression caused by overload resolution by updating the internal API calls.
- Updated the call in SpanHelpers.ByteMemOps.cs to use Buffer.MemmoveInternal.
- Renamed the internal method in Buffer.cs from Memmove to MemmoveInternal to resolve overload ambiguity.
Reviewed Changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.
File | Description |
---|---|
src/libraries/System.Private.CoreLib/src/System/SpanHelpers.ByteMemOps.cs | Updated the method call to use the newly renamed internal method. |
src/libraries/System.Private.CoreLib/src/System/Buffer.cs | Renamed the method to MemmoveInternal to clear up overload resolution issues. |
Comments suppressed due to low confidence (1)
src/libraries/System.Private.CoreLib/src/System/Buffer.cs:130
- Verify that renaming the internal method from 'Memmove' to 'MemmoveInternal' clarifies its intended use without breaking internal dependencies.
internal static unsafe void MemmoveInternal(ref byte dest, ref byte src, nuint len)
src/libraries/System.Private.CoreLib/src/System/SpanHelpers.ByteMemOps.cs
Show resolved
Hide resolved
/cc @jkotas |
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.
Thanks
Introduced by #113715
Fixes #114696
See #114696 (comment)
Thanks @tfenise