Update to the latest Rust nightly.

Cargo.toml

@@ -13,7 +13,7 @@ exclude = ["/.github", "ci"]
 keywords = ["linux"]
 
 [dependencies]
-c-gull = { version = "0.22.0", default-features = false, features = ["eyra"] }
+c-gull = { version = "0.22.1", default-features = false, features = ["eyra"] }
 
 [dev-dependencies]
 assert_cmd = "2.0.12"

README.md

@@ -110,7 +110,7 @@ Why not use Eyra?
 It might seem like "memory safety" might be a reason to use Eyra, and Eyra does
 have a lot of code written in safe Rust, so it does benefit some from Rust's
 memory safety. However, Eyra also has a lot of `unsafe` code (it's unavoidable
-for implementing a libc). Until this code has been more throughly proven, it's
+for implementing a libc). Until this code has been more thoroughly proven, it's
 not realistic to consider it more safe than mature C code.
 
 [Whole-program LTO]: https://github.com/sunfishcode/eyra/tree/main/example-crates/hello-world-lto#readme

rust-toolchain.toml

@@ -1,3 +1,3 @@
 [toolchain]
-channel = "nightly-2025-01-02"
+channel = "nightly-2025-04-28"
 components = ["rustc", "cargo", "rust-std", "rust-src", "rustfmt"]

tests/example_crates.rs

@@ -134,7 +134,7 @@ fn example_crate_eyra_panic_example() {
         &[],
         &[],
         "",
-        "thread 'main' panicked at src/main.rs:2:5:\nUh oh!\nnote: run with `RUST_BACKTRACE=1` environment variable to display a backtrace\n",
+        "\nthread 'main' panicked at src/main.rs:2:5:\nUh oh!\nnote: run with `RUST_BACKTRACE=1` environment variable to display a backtrace\n",
         Some(101)
     );
 }

tests/examples.rs

@@ -39,7 +39,7 @@ fn test_example(name: &str, features: &str, stdout: &str, stderr: &str) {
 
     let mut command = Command::new("cargo");
     if which::which("rustup").is_ok() {
-        command.arg("+nightly-2025-01-02");
+        command.arg("+nightly-2025-04-28");
     }
     command.arg("run").arg("--quiet");
     if !features.is_empty() {