Accepting integer arguments for Array::range?

Open
#525 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
rust
Domain
data

Research direction

Start by inspecting the Array::range and Linspace APIs and the discussion in issue #493, then review ndarray_for_numpy_users/index.html for the requested documentation context. Determine the intended behavior for integer arguments and whether the numpy.astype guidance should also be documented; done means the supported behavior or limitation is covered by appropriate tests and documentation.

Written by the indexing model from the issue text.

Description

enhancement

Right now I'm trying to pass integer arguments to Array::range. I have to first cast arguments to f32, then casting the result to int doesn't compile arr.mapv(|elem| elem as usize) does it work for Linspace<>?.

I noticed that range() works as I want for end<begin (unlike 5..1 which is empty). However https://github.com/rust-ndarray/ndarray/issues/493#issuecomment-424043912 indicates I will have to perform data copies on every single range() I call, which sounds like a waste of resources.

Why doesn't Array::range and Linspace accept integer values?

Dominant language
Rust
Stars
4.3k
Forks
391
PR merge metrics
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.