Named Tensors

Open
#599 16 comments 6 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
20/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
rust
Domain
data

Research direction

Read the linked Named Tensors blog post and HarvardNLP repository first, then compare the proposal with ndarray's current design. The issue does not identify files, tests, a concrete scope, or acceptance criteria, so a completed effort would first need those decisions.

Written by the indexing model from the issue text.

Description

enhancement

Hi,
Recently, HarvardNLP published a blogpost and proposed Named Tensors. The proposition is to name dimensions rather than using indexes. The repo is here.

Their second post shows how it is difficult to address such a problem once the framework is advanced.
Here is my proposing : What do you think about adding this functionality in ndarray ?

I think it is what future frameworks should aim, this project being young it seems the right timing.

Dominant language
Rust
Stars
4.3k
Forks
391
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from rust-ndarray/ndarray

All issues in rust-ndarray/ndarray

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.