Tracking Issue for no_std

Open
#1,496 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
20/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
rust
Domain
embedded-iot

Research direction

Start by reading issues #1487 and #708, then review rust-num/num-traits#197 for the related discussion. Investigate the std-only linspace dependency and the test-running problems mentioned here; done means the no_std tracking items have an agreed scope and the affected tests or compatibility work are addressed.

Written by the indexing model from the issue text.

Description

tracking-issue

Just so I can keep track of a few things:

  • Some issues running tests with #1487
  • Mainly caused by linspace only being available with feature = "std"
  • See #708 for the originating issue for us
  • See rust-num/num-traits#197 for the corresponding discussion that ndarray contributors had started with num-traits
Dominant language
Rust
Stars
4.3k
Forks
391
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from rust-ndarray/ndarray

All issues in rust-ndarray/ndarray

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.