JuliaArrays / JuliaArrays/StructArrays.jl
Feature request: Base.empty and Base.emptymutable
Nobody has claimed this yet.
- Dominant language
- Julia
- Stars
- 402
- Forks
- 49
- PR merge metrics
- No merged PRs in 30d
Description
Some generic functions, like in SplitApplyCombine.jl, construct their return values from Base.empty or Base.emptymutable. It would be nice if these were implemented for StructArrays to not always end up with Arrays of Structs.
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 by reading the relevant generic functions in SplitApplyCombine.jl and checking how StructArrays currently handle Base.empty and Base.emptymutable. The issue does not name implementation files or tests, so locate existing StructArrays tests for empty-like operations before defining the expected behavior. Done means these functions preserve StructArrays instead of producing arrays of structs.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- julia
- Domain
- data
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100