JuliaAI / JuliaAI/MLJModelInterface.jl
Do we really need a `training_losses` fallback?
Open
Nobody has claimed this yet.
- Dominant language
- Julia
- Stars
- 39
- Forks
- 8
- PR merge metrics
- No merged PRs in 30d
Description
We already have supports_training_losses. It also seems that documentation does not require the fallback, but this should be checked.
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
Search the package for training_losses and supports_training_losses, then inspect the documentation to determine whether the fallback is required. Done means the fallback's necessity is established and the resulting change or decision is clearly recorded.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- julia
- Domain
- tooling
- Issue type
- Refactor
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 28/100