depwarns please
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 45/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- julia
- Domain
- developer-experience
Research direction
Start with the Polynomials.PolyCompat entry point and inspect how the deprecated Poly API and missing polyeval name are handled. Update the deprecation and missing-name guidance to point to Polynomial and Polynomial(...)(...), then verify the resulting messages in the relevant compatibility tests, if present.
Written by the indexing model from the issue text.
Description
i really like the new API, whereby one creates a polynomial with Polynomial instead of Poly and then evaluates it as a functor instead of calling polyeval. thanks for that!
however, upgrading is more difficult than it needs to be. one has to read the documentation! gheesh. would be more discoverable were there better deprecation warnings. currently, it just says Poly is deprecated and polyeval is not found. how about saying "use Polynomial instead of Poly" and "use Polynomial(...)(...) instead of polyeval" ?
julia> using Polynomials.PolyCompat
help?> Poly
search: Poly poly polyval polyint polyfit polyder PolyCompat @polly evalpoly @evalpoly
Poly{T}
Type of polynomial to support legacy code. Use of this type is not encouraged.
This type provides support for poly, polyval, polyder, and polyint to support older code. It
should not be used for a new code base. Call using Polynomials.PolyCompat to enable this
module.
help?> polyeval
search:
Couldn't find polyeval
Perhaps you meant polyval, padeval or polyder
No documentation found.
Binding polyeval does not exist.
- Dominant language
- Julia
- Stars
- 321
- Forks
- 81
- Avg merge
- 10h 1m
- Merged PRs (30d)
- 5
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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.
More from JuliaMath/Polynomials.jl
-
Difficulty 1/5 Under an hour Newbie friendliness 83/100
JuliaMath/Polynomials.jl#647 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
JuliaMath/Polynomials.jl#641 · 1 comment ·
-
tagbot-manual
Difficulty 2/5 1-3 hours Newbie friendliness 35/100
JuliaMath/Polynomials.jl#627 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 38/100
JuliaMath/Polynomials.jl#620 · 6 comments ·
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
JuliaMath/Polynomials.jl#585 · 7 comments ·
All issues in JuliaMath/Polynomials.jl
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 83/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
JuliaDecisionFocusedLearning/ImplicitDifferentiation.jl#231 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
bug io
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
lanl-ansi/PowerModels.jl#1023 ·