fix events::adding_and_removing_listeners test failure in release mode

best guess is that release mode optimizations collapsed these two
functions into one, because in release mode the assertion that would
fail was:

    assert!(listeners.add(other_dummy_listener));

which would mean that `listeners.add()` thought it was trying to add
a duplicate listener function.

adding dummy println's is a simple way to ensure that the compiler
won't try to collapse these thinking that they are the same function.

ggdt/src/events/mod.rs

@@ -175,10 +175,12 @@ mod tests {
 	}
 
 	fn dummy_listener(_event: &TestEvent, _context: &mut DummyContext) -> bool {
+		println!("dummy_listener event fired");
 		false
 	}
 
 	fn other_dummy_listener(_event: &TestEvent, _context: &mut DummyContext) -> bool {
+		println!("other_dummy_listener event fired");
 		false
 	}
 

ggdt/src/graphics/bitmap/rgb/triangles.rs

@@ -1,5 +1,5 @@
 use std::simd;
-use std::simd::{SimdFloat, SimdUint};
+use std::simd::prelude::{SimdFloat, SimdUint};
 
 use crate::graphics::{edge_function, per_pixel_triangle_2d, BlendFunction, RgbaBitmap, RGBA};
 use crate::math::Vector2;

ggdt/src/graphics/color.rs

@@ -1,6 +1,6 @@
 use std::ops::{Mul, MulAssign};
 use std::simd;
-use std::simd::{SimdFloat, SimdUint};
+use std::simd::prelude::{SimdFloat, SimdUint};
 
 use byteorder::{ReadBytesExt, WriteBytesExt};
 

ggdt/src/math/mod.rs

@@ -1,6 +1,6 @@
 use std::ops::{Add, Div, Mul, Sub};
 use std::simd;
-use std::simd::{SimdFloat, SimdPartialOrd};
+use std::simd::prelude::{SimdFloat, SimdPartialOrd};
 
 mod circle;
 mod matrix3x3;

rust-toolchain.toml

@@ -4,4 +4,4 @@
 # necessarily see a reason to keep using whatever nightly version is the latest, and would
 # prefer stick with versions that appear to be stable and just periodically do manual updates
 # here to get *some* peace of mind in terms of build stability.
-channel = "nightly-2023-11-10"
+channel = "nightly-2024-09-05"