JuliaData / JuliaData/PooledArrays.jl
ambiguity in vcat
Open
Nobody has claimed this yet.
- Dominant language
- Julia
- Stars
- 49
- Forks
- 11
- PR merge metrics
- No merged PRs in 30d
Description
We currently have the following design issue:
julia> vcat([1,2,3], PooledArray([1,2,3]))
ERROR: MethodError: vcat(::Vector{Int64}, ::PooledVector{Int64, UInt32, Vector{UInt32}}) is ambiguous.
julia> vcat(PooledArray([1,2,3]), [1,2,3])
ERROR: MethodError: vcat(::PooledVector{Int64, UInt32, Vector{UInt32}}, ::Vector{Int64}) is ambiguous.
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 reproducing both vcat calls shown in the issue in Julia and inspect how dispatch selects methods for Vector and PooledArray arguments. Determine the intended behavior for each argument order; the issue is complete when both examples have an unambiguous, agreed-upon result.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- julia
- Domain
- data
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100