Allow Unset arrays
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 126
- Forks
- 6
- PR merge metrics
- No merged PRs in 30d
Description
Right now when an array is declared it'll have an initial value that is an array of unsets. But if we don't initialize anything, this is a bit of a waste, and could lead to unneccesary OOMs. (Think arrays representing large memory blocks). Instead, allow an array itself to be Unset, and only fill it out when an element is actually needed.
Ties into #159
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
Start by reading the array initialization and unset-value handling in the compiler, then follow the relationship to issue #159. The change is complete when an uninitialized array can remain Unset without eagerly creating an array of unsets, while elements become available when they are actually needed.
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