Within Vector, use Array.Copy wherever possible

[jdunkerley]

Pull Request Description

Following the Slice and Array.Copy experiment, took just the Array.Copy parts out and built into the Vector class.

This gives big performance wins in common operations:

Test	Ref	New
New Vector	41.5	41.4
Append Single	26.6	4.2
Append Large	26.6	4.2
Sum	230.1	99.1
Drop First 20 and Sum	343.5	96.9
Drop Last 20 and Sum	311.7	96.9
Filter	240.2	92.5
Filter With Index	364.9	237.2
Partition	772.6	280.4
Partition With Index	912.3	427.9
Each	110.2	113.3

Benchmarks run on an AWS EC2 r5a.xlarge with 1,000,000 item count, 100 iteration size run 10 times.

Important Notes

Have generally tried to push the @Tail_Call down from the Vector class and move to calling functions on the range class.

• Expanded benchmarks on Vector
• Added take method to Vector
• Added each_with_index method to Vector
• Added filter_with_index method to Vector

Checklist

Please include the following checklist in your PR:

• The documentation has been updated if necessary.
• All code conforms to the Scala, Java, and Rust style guides.
• All documentation and configuration conforms to the markdown and YAML style guides.
• All code has been tested where possible.

[radeusgd]

Apart from reconsidering the slice name, the rest looks good to me.

Hurray for the performance improvements! 🎉

[wdanilo]

Absolutely amazing results ❤️

[jdunkerley]

Discovered an issue with polyglot arrays and Array.Copy.

from Standard.Base import all

main =
    vector = "ABCDEF".utf_8
    IO.println <| vector == [65,66,67,68,69,70]

    new_array = Array.new 6
    Array.copy vector.to_array 0 new_array 0 6
    new_vector = Vector.Vector new_array
    IO.println <| new_vector == [65,66,67,68,69,70]

Will print True for the first check and False for the second.

Raised a ticket to look at the way polyglot arrays are used in vector and solve this issue:
https://www.pivotaltracker.com/story/show/181122542

[wdanilo]

Discovered an issue with polyglot arrays and Array.Copy. Can't merge until solved.

In such a case, James, please always do the following steps:

1. Change the PR to Draft.
2. Add description in the comment what is the issue. Telling only Discovered an issue with polyglot arrays and Array.Copy does not allow threader to understand what it is about.
3. Paste in the comment a link to the issue, so everyone can track whether it was resolved or not.

[radeusgd]

Enso code looks good, I don't understand how the workaround fixes the described Array.copy issue though. But I'm told cases that didn't work, work now.

I think @kustosz should take a look at this before merge too.

[jdunkerley]

Revised stats:

Test	Ref	New
New Vector	36.1	36.5
Append Single	19.4	4.5
Append Large	13.4	5.3
Sum	208.6	123.1
Drop First 20 and Sum	489.1	116.4
Drop Last 20 and Sum	474.7	115.8
Filter	228.9	103.6
Filter With Index	380.7	188.7
Partition	714.4	307.7
Partition With Index	870.2	423.8
Each	111.0	113.6

[kustosz]

LGTM, though I hope my proposed fix for Array.copy works and un-breaks all of this :)