[RFC]: Move `from_arraybuffer.js` into `@stdlib/ndarray/from-arraybuffer`
- 主要言語
- JavaScript
- スター
- 6k
- フォーク
- 1.3k
- 平均マージ
- 1日 3時間
- マージ済み PR(30日)
- 611
説明
### Description
This RFC proposes acting on the `TODO` in `lib/from_arraybuffer.js`, which notes the helper should move to `@stdlib/ndarray/from-arraybuffer`.
The file is dimension-agnostic and is copied verbatim into each dimensional `ctor` package. There are three copies today, in `vector/ctor`, `matrix/ctor`, and `tensor3d/ctor`. Adding `tensor4d` and `tensor5d` would make five.
Separate work on `@stdlib/ndarray/from-arraybuffer` is already under way, which would reclaim all of them at once.
### Related Issues
Related issues: Parent
### Questions
Should this land before `tensor4d` starts, so the count stops at three?
### Other
No.
### Checklist
- [x] I have read and understood the [Code of Conduct](https://github.com/stdlib-js/stdlib/blob/develop/CODE_OF_CONDUCT.md).
- [x] Searched for existing issues and pull requests.
- [x] The issue name begins with `RFC:`.
コントリビューションガイド
調査の方向性
Start by reading lib/from_arraybuffer.js and its copies in vector/ctor, matrix/ctor, and tensor3d/ctor, then inspect the separate @stdlib/ndarray/from-arraybuffer work already under way. Done means the helper has been moved there and the dimensional packages no longer carry these duplicate copies before tensor4d and tensor5d are added.
索引モデルが issue の本文から書いたものです。
評価
- 技術スタック
- javascript
- 領域
- data
- issue の種類
- リファクタリング
- 難易度
- 3/5
- 見積もり時間
- 1〜2日
- 活発さ
- 活発
- 明瞭さ
- おおむね明確
- 初心者へのやさしさ
- 35/100