You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Blocking: trait conflicts (#322) cause user-facing breakage today; type unification unblocks everything
P1
⚡ Performance & Memory
The unsafe removal (#368) is actively tracked; perf gap vs scikit-learn (#261) erodes adoption
P1
🖥️ DX, Display & Docs
Low-effort, high-visibility; good first issues; #256 (logistic regression panic) is a bug
P2
🌲 Trees & Ensembles
Most-used models; sample weights and variable importance are highly requested
P2
📐 Linear Models & Solvers
Completes the regression/classification surface; solvers (#70, #63) are well-specified
P3
🔧 Data I/O & Interop
ndarray bridge (#326) and parquet (#249) open up real pipeline usage; streaming is complex
P4
🧩 New Algorithms
Valuable but requires stable foundation; HDBSCAN, multiclass SVC, and RFE are highest demand
The single highest-impact starting point is #322 + #219 (trait bound and number trait cleanup), since they directly break user workflows and their resolution would unblock correct cross-validation for tree models. Immediately after, the #256 logistic regression panic should be treated as a bug fix given its user impact.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
Plan to version 1.0.0
https://github.com/smartcorelib/smartcore/issues?page=1
Here is a comprehensive plan to organise the 52 open issues in smartcorelib/smartcore.
Issues to Close
These issues are either too vague, exploratory dead-ends, near-duplicates, or out of scope for a focused ML library:
anyinputstd::memsize/alignment analysisMacro-Issues with Sub-Issues
Group actionable issues into 7 macro-themes:
🧱 1. Core API & Type System Cleanup
Foundation work that unblocks everything else.
FloatNumber/RealNumbertraitsRandomForest::fitvs metricsnew()withDefault::default()in traitsDefault::default()⚡ 2. Performance & Memory
Optimisation work for real-world scale.
unsafefromiterator_mut(safesplit_at_mut)slipstreamand ILP #284) — Investigateslipstreamand ILPargsortvsquick_sortperformance[T]slices instead ofVecinArraytrait🌲 3. Tree Models & Ensembles
High-demand improvements to the most-used model family.
📐 4. Linear Models & Solvers
Completing the linear algebra and regression stack.
rust_decimalsupport (non-float arithmetic)🔧 5. Data I/O & Interoperability
Making smartcore work in real pipelines.
DenseMatrix::from_ndarray2convenience method🖥️ 6. DX, Display & Documentation
Developer experience and discoverability.
Displayimpl forArray/Array2DisplayforNaiveBayesDisplayforDatasetderive_builderfor model parameters🧩 7. New Algorithms
Expanding coverage for ML practitioners.
constcontext investigationPriority Order for Implementation
unsaferemoval (#368) is actively tracked; perf gap vs scikit-learn (#261) erodes adoptionThe single highest-impact starting point is #322 + #219 (trait bound and number trait cleanup), since they directly break user workflows and their resolution would unblock correct cross-validation for tree models. Immediately after, the #256 logistic regression panic should be treated as a bug fix given its user impact.
Beta Was this translation helpful? Give feedback.
All reactions