Get rid of new_uninitialized and new_uninitialized_generic.
- Dominant language
- Rust
- Stars
- 4.8k
- Forks
- 565
- PR merge metrics
- No merged PRs in 30d
Description
The two unsafe functions [Matrix::new_uninitialized](https://github.com/rustsim/nalgebra/search?q=new_uninitialized&unscoped_q=new_uninitialized) and [Matrix::new_uninitialized_generic](https://github.com/rustsim/nalgebra/search?q=new_uninitialized_generic&unscoped_q=new_uninitialized_generic) are used when we don't care about the initial value of a matrix/vector because they will be overwritten by the result of other operations. We use them mostly for performance reasons to avoid an unnecessary initialization step.
However, this is the most significant blocker for https://github.com/rustsim/nalgebra/issues/282. So if we ever want to support non-Copy types, this is the first thing to address in a way that does not hurt performance for Copy types.
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.