stdlib-js / stdlib-js/stdlib

[RFC]: Move `from_arraybuffer.js` into `@stdlib/ndarray/from-arraybuffer`

Offen
#14,965 3 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen
Feature JavaScript priority: Low
Vorherrschende Sprache
JavaScript
Sterne
6k
Forks
1.3k
Ø Merge
1 T. 3 Std.
Gemergte PRs (30 T.)
611

Beschreibung

### 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:`.

Beitragsleitfaden

Beitragsleitfaden öffnen

Rechercherichtung

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.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Bewertung

Tech-Stack
javascript
Bereich
data
Issue-Typ
Refactoring
Schwierigkeit
3/5
Geschätzter Aufwand
1-2 Tage
Aktivitätsstatus
Aktiv
Klarheit
Größtenteils klar
Anfängerfreundlichkeit
35/100

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.