chore(array): optmize array_splice

[cnjhb]

This might reduce the overhead of some memcpy calls.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 90.46%. Comparing base (94d38e6) to head (4567b8c).

Additional details and impacted files

@@            Coverage Diff             @@
##           master    #4088      +/-   ##
==========================================
+ Coverage   90.45%   90.46%   +0.01%     
==========================================
  Files         941      941              
  Lines       60385    60386       +1     
  Branches     1145     1145              
==========================================
+ Hits        54621    54631      +10     
+ Misses       5254     5248       -6     
+ Partials      510      507       -3     

see 3 files with indirect coverage changes

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[actionless]

i wonder should it be moved here to just change count from >= to > 0?

[cnjhb]

No, passing 0 is indeed a valid operation.
array_take is what passes 0.

[cnjhb]

Passing 0 to count means that no elements are inserted into the array.
Just like with array_take, if you only need to remove some elements from the array, you can pass 0 to count.

[cnjhb]

This optimization is actually quite useful;
every array_remove and array_take call can benefit from it.