Rutam

Results 35 comments of Rutam

Got all tests passing except the data buffer accessors one: ![image](https://github.com/stdlib-js/stdlib/assets/138517416/a7e9cf36-956b-49df-9d9e-8bff4ed148a2)

It logged (additionally, dt is: `complex64`): ``` the function converts an array to a standardized object (data buffer accessors) x: Complex64Array {} isAccessorArray(x): false √ returns expected value √ returns...

Also, logging the same test value for `lib/main.js` of `is-accessor-array` is giving false to me: ```javascript var x = new Complex64Array( 10 ); console.log(isAccessorArray(x)); ``` Additionally, logging `Array.isArray(value.accessors)` is giving...

This is resolved, thank you @kgryte! I have fixed the implementation. Also, just to confirm, accessor tests are mainly testing the stride support (x, y, negative) and the main implementation...

> You use convert a normal array to an accessor array using `@stdlib/array/base/to-accessor-array`. So, the current tests for `grot` and also `gcopy`, `gswap` use Complex128 for accessor tests. And `to-accessor-array`...

Edit: Now that I think about it, maybe we shouldn't use Complex128 for the accessor tests actually cause if we do, we have to set the values for `x` and...

> Yes, but you'll want to add separate complex array tests, as the algorithm, IIRC, is different depending on whether real or complex. oh, yeah right this is what I...

Hello, I have to do some styling changes in the package like spaces before any kind of brackets in the JS implementations and write `README.md` but since I got some...

Hey, @PATHAKAAKASH19, I think you'll need to take this up with the maintainers of the repository.

Hello, thought I should just push a draft PR for one namespace and receive feedback before moving to another in the package in ndarray! Also, I have these questions: 1....