Split array.delete_many() void to array.delete_many() array and array.delete_many_in_place() void

[i582]

Describe the feature

Current method has very unexpected behaviour.

I would expect two kinds of functions. The first one changes the passed array without allocations for new arrat, in place. The second creates a copy and returns it, so that it is clear that a copy is being created.
Here we have the second behavior, however, the assignment to an array that changes is hidden from the user's eyes. I think this is bad behavior, as it can lead to hard-to-catch bugs

Use Case

See above

Proposed Solution

Let's split to two methods:

// delete_many deletes `size` elements beginning with index `i` and return new array.
pub fn (a array) delete_many(i int, size int) array

and

// delete_many_in_place deletes `size` elements beginning with index `I`
// in place.
pub fn (mut a array) delete_many_in_place(i int, size int)

Other Information

No response

Acknowledgements

• I may be able to implement this feature request
• This feature might incur a breaking change

Version used

V 0.3.3 21b17fe.d563739

Environment details (OS name and version, etc.)

OS: macos, macOS, 13.0.1, 22A400
Processor: 10 cpus, 64bit, little endian, Apple M1 Pro
CC version: Apple clang version 14.0.0 (clang-1400.0.29.202)

getwd: /Users/petrmakhnev
vmodules: /Users/petrmakhnev/.vmodules
vroot: /Users/petrmakhnev/v
vexe: /Users/petrmakhnev/v/v
vexe mtime: 2023-01-31 09:57:40
is vroot writable: true
is vmodules writable: true
V full version: V 0.3.3 21b17fe.d563739

Git version: git version 2.37.1 (Apple Git-137.1)
Git vroot status: weekly.2023.04-39-gd5637392
.git/config present: true