Views and operations with mixed scalar types
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
Research direction
Start by reviewing the proposed RawData trait, ArrayBase storage pointer, and Index implementation changes in the issue. Assess whether they can support views exposing a different scalar type and mixed-type operations without breaking existing ndarray behavior. Done would be a maintainer-backed design decision with clear API and implementation boundaries.
Written by the indexing model from the issue text.
Description
I'm curious about the feasibility of extending ndarray to support mixed-precision and mixed-domain algorithms. I was thinking of syntax something like this, enabling a view to offer up f64 values despite the backing storage being f32 (for example).
let a: Array1<f64> = array![1., 2., 3.];
let b: Array1<f32> = array![4., 5., 6.];
let c = a + b.view_as::<f64>();
I'm a Rust novice and ran into some trouble (attempting to use associated_type_defaults to avoid more disruptive changes)
pub unsafe trait RawData: Sized {
/// The array element type.
type Elem: From<Self::ElemMem>;
type ElemMem;
where ArrayBase would have
ptr: std::ptr::NonNull<S::ElemMem>,
and the Index implementation becomes
fn index(&self, index: I) -> &S::Elem {
debug_bounds_check!(self, index);
unsafe {
&S::Elem::from(*self.ptr.as_ptr().offset(
index
.index_checked(&self.dim, &self.strides)
.unwrap_or_else(|| array_out_of_bounds())
))
}
}
I'm curious whether
- this sort of feature to support mixed precision is of interest to include in ndarray, and
- this implementation strategy seems like a reasonable way to go about it.
- 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
- 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 rust-ndarray/ndarray
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
rust-ndarray/ndarray#1612 · 1 comment ·
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
rust-ndarray/ndarray#1617 · 1 comment ·
-
bug good first issue
Difficulty 3/5 1-2 days Newbie friendliness 68/100
rust-ndarray/ndarray#1615 · 1 comment ·
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
rust-ndarray/ndarray#1610 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 72/100
rust-ndarray/ndarray#1609 ·
All issues in rust-ndarray/ndarray
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
kwakseongjae/auto-hwp#319 ·
-
area:cli bug filter-quality good first issue priority:medium
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
-
Difficulty 1/5 Under an hour Newbie friendliness 72/100
bevyengine/bevy#25861 ·
-
comp-datalake
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
ClickHouse/ClickHouse#121222 ·
-
enhancement remote
Difficulty 2/5 1-3 hours Newbie friendliness 68/100