Document Strict Tensor Shape Matching Requirements

Open Beginner friendly
#93 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
68/100
Issue type
Documentation
Clarity
Mostly clear
Activity status
Active
Domain
compilers, documentation

Research direction

Start with README.md or the language specification and review the semantic analysis behavior described in the issue. Document that tensor dimensions must match exactly during assignment, including the Tensor and Tensor<f64, [4, 4]> example, and record the future decision about implicit casting or broadcasting rules.

Written by the indexing model from the issue text.

Description

core-lang documentation good first issue

Our semantic analysis now strictly enforces that tensor dimensions match exactly during assignment (e.g., Tensor<f64> vs Tensor<f64, [4, 4]>). This is a breaking change for .vx programs that previously relied on implicit or lax shape propagation.

Action: Formally document this behavior in the README.md or language specification document. Decide whether implicit casting or broadcasting rules should be implemented in the future.

Dominant language
Rust
Stars
14
Forks
2
Avg merge
12h 9m
Merged PRs (30d)
78

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 vx-lang/Vx

All issues in vx-lang/Vx

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.