JuliaCollections / JuliaCollections/AbstractTrees.jl
`filter` and/or `filter!`
Nobody has claimed this yet.
- Dominant language
- Julia
- Stars
- 243
- Forks
- 67
- PR merge metrics
- No merged PRs in 30d
Description
Would it make sense for this package to define filter and/or filter!?
I've looked into the implementation and guess that this issue boils down to: Is there a kind of null element defined for abstract trees? If yes, then a PreOrderDFS could replace elements by null and that should work, I think.
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 reviewing the package's tree interfaces and the PreOrderDFS implementation, focusing on whether abstract trees define a null element. Determine the intended semantics and API for filter and filter!, then confirm the scope and acceptance criteria before attempting implementation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- julia
- Domain
- data
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100