-
Notifications
You must be signed in to change notification settings - Fork 832
Bugfix for Array.insertManyAt returns original array for empty inserion (#18352) #18353
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
Conversation
❗ Release notes required
|
|
Hi @muqiuhan - thanks for the contribution. Could you please add a test for the fix? |
|
On Mon, 03 Mar 2025 03:21:35 -0800 Petr ***@***.***> wrote:
psfinaki left a comment (dotnet/fsharp#18353)
Hi @muqiuhan - thanks for the contribution. Could you please add a
test for the fix?
Sure, I added a test to cover this change in `Array.insertManyAt`
|
|
👍 |
psfinaki
left a comment
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.
Alrighty, I think this is the right fix.
Please add release notes and optionally a comment for the change, referencing the issue.
Thanks!
…ion (dotnet#18352) - Update test, release note and comment for Array.InsertManyAt
|
/azp run |
|
Azure Pipelines successfully started running 2 pipeline(s). |
|
/azp run |
|
Azure Pipelines successfully started running 2 pipeline(s). |


Description
Use
array.Clone()to fix the bug thatArray.insertManyAtdirectly returning source array when the values inserted are empty.Checklist