Reversing of array index ordering.
Open
Nobody has claimed this yet.
breaking
enhancement
Language Design
- Dominant language
- Rust
- Stars
- 126
- Forks
- 6
- PR merge metrics
- No merged PRs in 30d
Description
Currently SUS treats arrays as just another type of another type, but hardware design experience has shown that arrays are so commonly used, and object-oriented features are not used, that it's possible to make "a type with several arrays stuck to it" it's own primitive. With this, we can make the type declaration int[5][20] a the same order as the usage: a[4][15]
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files, tests, or entry points are identified in the issue. The requested behavior is complete when declarations such as int[5][20] a use the same index ordering as accesses such as a[4][15].
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- compilers
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100