Consider making `valarray` representation two pointers instead of pointer and size
Open
Nobody has claimed this yet.
performance
vNext
- Dominant language
- C++
- Stars
- 11.1k
- Forks
- 1.7k
- Avg merge
- 4d 15h
- Merged PRs (30d)
- 22
Description
Advantages:
- Should not suffer from the vectorization issue that needs member caching to a local variable commented in #3968
- Matches libc++ representation
vNext note: Resolving this issue will require breaking binary compatibility. We won't be able to accept pull requests for this issue until the vNext branch is available. See #169 for more information.
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
Read #3968 for the vectorization concern and #169 for the vNext and binary-compatibility requirements. Once the vNext branch is available, inspect the valarray representation and determine the compatibility implications. Done means the representation uses two pointers without regressing the discussed behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- compilers
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100