JuliaImages / JuliaImages/ImageFeatures.jl
Dependency on Images.jl directly
Nobody has claimed this yet.
- Dominant language
- Julia
- Stars
- 49
- Forks
- 31
- PR merge metrics
- No merged PRs in 30d
Description
I realize this may be an odd question.
It came up in https://github.com/JuliaImages/Images.jl/issues/682#issuecomment-345318420 that ImageFeatures.jl depends on Images.jl, and I found this quite surprising because my mental image for Images.jl so far was as a convenient meta package for importing the whole ecosystem.
So I just felt like double checking this wouldn't hurt. Is there a reason that this package needs to depend on Images.jl directly, instead of the individual backend packages? I quickly browsed through the source files and didn't see any obvious reason like extending a function.
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
Audit the source files and dependency declarations to determine whether ImageFeatures.jl uses APIs that require a direct dependency on Images.jl. Compare the current usage with the individual backend packages, then verify that removing the unnecessary dependency preserves the existing package behavior and tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- julia
- Domain
- computer-vision
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100