[sarthakkaushik927]

Description

What is the purpose of this pull request?

This pull request:

• fixes the with method in array/fixed-endian-factory, which created the returned array from the same underlying ArrayBuffer as the source array. As a consequence, (1) setting the new value mutated the source array and (2) for arrays which are views on a buffer having a non-zero byte offset and/or a shorter length, the returned array had the wrong length and the new value was written at the wrong position.

  var Float64ArrayFE = fixedEndianFactory( 'float64' );
  
  var arr = new Float64ArrayFE( 'little-endian', [ 1.0, 2.0, 3.0 ] );
  var out = arr.with( 0, 99.0 );
  
  var str = arr.toString();
  // before: '99,2,3'
  // after: '1,2,3'
  
  var buf = new ArrayBuffer( 32 );
  arr = new Float64ArrayFE( 'little-endian', buf, 8, 2 );
  arr.set( [ 5.0, 6.0 ] );
  out = arr.with( 0, 7.0 );
  
  str = out.toString();
  // before: '7,5,6,0'
  // after: '7,6'

• copies the source elements into a newly allocated array before setting the provided value, and adds regression tests for source mutation, views on a buffer, and byte order preservation.

Related Issues

Does this pull request have any related issues?

No.

Reference Packages

Did the content of this pull request follow one or more existing packages? Answering is optional.

This pull request followed these packages:

• array/fixed-endian-factory (existing filter and map methods)

What carried over from the reference(s)?

• element-wise copying via the data view getter/setter and test structure

What differed, or what did you have to work out yourself?

• none.

Questions

Any questions for reviewers of this pull request?

No.

Other

Any other information relevant to this pull request? This may include screenshots, references, and/or implementation notes.

No.

Checklist

Please ensure the following tasks are completed before submitting this pull request.

• Read, understood, and followed the contributing guidelines.

AI Assistance

When authoring the changes proposed in this PR, did you use any kind of AI assistance?

• Yes
• No

If you answered "yes" above, how did you use AI assistance?

• Code generation (e.g., when writing an implementation or fixing a bug)
• Documentation (including examples)
• Test/benchmark generation
• Research and understanding

Disclosure

If you answered "yes" to using AI assistance, please provide a short disclosure indicating how you used AI assistance. This helps reviewers determine how much scrutiny to apply when reviewing your contribution.

I used Claude Code to help generate the tests and documentation. I reviewed all changes and ran the package tests locally.

---

@stdlib-js/reviewers

[kgryte]

Left initial comments.

[stdlib-bot]

Coverage Report

Package	Statements	Branches	Functions	Lines
array/fixed-endian-factory	$\\color{red}1238/1445$ $\\color{green}+85.67\\%$	$\\color{red}161/185$ $\\color{green}+87.03\\%$	$\\color{red}25/33$ $\\color{green}+75.76\\%$	$\\color{red}1238/1445$ $\\color{green}+85.67\\%$

The above coverage report was generated for the changes in this PR.

[kgryte]

As the CI failure is not due to changes introduced in this PR, I'll go ahead and merge.