Closed bluss closed 5 years ago
Doesn't seem to be wholly fixed in the nightly channel. Using uninitialized or zeroed still is better than the [[0.; n]; m]
literal.
This bug remained in Rust 1.18 but it is fixed in Rust 1.21. So somewhere there, it was fixed again.
See issue #9
The base issue is now fixed in current nightly channel, but remains in beta channel for now, so the workaround has to stay. It may be backported to beta, otherwise we have to wait until current nightly graduates to stable.