Undefined behavior in tests

[GnomedDev]

decancer/core/src/tests.rs

Line 233 in 3f4e7df

range: MaybeUninit::uninit().assume_init(),

This is always undefined behavior, as although not read it is still a value that is being created and passed to llvm as noundef. This will cause aborts in a couple Rust versions, when this pattern is compiled to ud2 (undefined instruction, abort instantly).

This is already being caught by running clippy locally, which I suggest is added to CI, under the clippy::uninit_assumed_init lint.

[FlareFlo]

Running miri reports the following:
MIRIFLAGS="-Zmiri-disable-isolation" cargo +nightly miri nextest run --test-threads 20

--- STDERR:              decancer tests::isolating_run_sequences ---
error: Undefined Behavior: using uninitialized data, but this operation requires initialized memory
   --> src/tests.rs:233:14
    |
233 |       range: MaybeUninit::uninit().assume_init(),
    |              ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ using uninitialized data, but this operation requires initialized memory
    |
    = help: this indicates a bug in the program: it performed an invalid operation, and caused Undefined Behavior
    = help: see https://doc.rust-lang.org/nightly/reference/behavior-considered-undefined.html for further information
    = note: BACKTRACE on thread `tests::isolatin`:
    = note: inside `tests::isolating_run_sequences` at src/tests.rs:233:14: 233:49

[null8626]

Hai! Thank you so much for this. ❤️

[null8626]

Fixed in 967467c!