JuliaApproximation / JuliaApproximation/FastTransforms.jl
big chebyshevu
Open
Nobody has claimed this yet.
- Dominant language
- Julia
- Stars
- 281
- Forks
- 27
- PR merge metrics
- No merged PRs in 30d
Description
julia> plan_chebyshevutransform(big.([1.,2.]))
ERROR: MethodError: no method matching plan_chebyshevutransform(::Vector{BigFloat}, ::Val{1})
Closest candidates are:
plan_chebyshevutransform(::AbstractVector{T}, ::Val{1}) where T<:Union{Float32, Float64, ComplexF32, ComplexF64} at /Users/sheehanolver/.julia/packages/FastTransforms/47F6t/src/chebyshevtransform.jl:250
plan_chebyshevutransform(::AbstractVector{T} where T) at /Users/sheehanolver/.julia/packages/FastTransforms/47F6t/src/chebyshevtransform.jl:263
Stacktrace:
[1] plan_chebyshevutransform(x::Vector{BigFloat})
@ FastTransforms ~/.julia/packages/FastTransforms/47F6t/src/chebyshevtransform.jl:263
[2] top-level scope
@ REPL[68]:1
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 with the failing plan_chebyshevutransform(::Vector{BigFloat}) call and inspect the method definitions in chebyshevtransform.jl around lines 250 and 263. Confirm how the existing supported numeric types are handled; done means the BigFloat example no longer raises the shown MethodError and has corresponding coverage if an existing test location is found.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- julia
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100