JuliaArrays / JuliaArrays/StaticArrays.jl
specialized Base.copymutable method?
Open
Nobody has claimed this yet.
- Dominant language
- Julia
- Stars
- 844
- Forks
- 159
- Avg merge
- 3d 21h
- Merged PRs (30d)
- 3
Description
Base.copymutable(a::SVector) currently works using its default method, which calls similar(a) followed by copyto!.
Might it be slightly faster to have a specialized copymutable(a) for isbits types (#799) that calls MVector(a)?
Contributor guide
No contributing guide indexed for this repository
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 at Base.copymutable for SVector and trace the default similar(a) followed by copyto! path. Compare it with MVector(a) for isbits types, using issue #799 as context, and measure whether the specialized method is actually faster. Done means a justified implementation decision supported by the comparison.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- julia
- Domain
- performance
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100