Skip to content

fixed the invalid scancode transmute#1503

Merged
jagprog5 merged 1 commit into
Rust-SDL2:masterfrom
Rismosch:fix/invalid-scancode-transmute
Oct 27, 2025
Merged

fixed the invalid scancode transmute#1503
jagprog5 merged 1 commit into
Rust-SDL2:masterfrom
Rismosch:fix/invalid-scancode-transmute

Conversation

@Rismosch
Copy link
Copy Markdown
Contributor

@Rismosch Rismosch commented Oct 6, 2025

removed an invalid transmute, that causes a panic in rustc v.1.90.0

related issue: #1501

@jagprog5
Copy link
Copy Markdown
Contributor

@Cobrand @antonilol looks good to me. same form of fix as my previous one here.

@jagprog5 jagprog5 merged commit 1fac15b into Rust-SDL2:master Oct 27, 2025
12 of 17 checks passed
@iddm
Copy link
Copy Markdown
Contributor

iddm commented Dec 8, 2025

Hey guys! I would be so glad if you could release a 0.38.1 containing the fix!

@antonilol
Copy link
Copy Markdown
Contributor

Hey guys! I would be so glad if you could release a 0.38.1 containing the fix!

Should be possible, but the build is currently broken on windows (and mac maybe) (see #1511), so this would have to be backported on 0.38.0 to prevent including the breaking changes on crates.io (if it isn't broken there already, don't know exactly what caused it).

@Cobrand would have to release it, I am not an owner on crates.io.

@antonilol
Copy link
Copy Markdown
Contributor

@iddm Note that a crate does not have to be on crates.io (only when publishing there). You can add dependencies from any git repo to Cargo.toml, see https://doc.rust-lang.org/cargo/reference/specifying-dependencies.html#specifying-dependencies-from-git-repositories.

@iddm
Copy link
Copy Markdown
Contributor

iddm commented Dec 10, 2025

Yes, this is what I am doing now, but I prefer to depend on semversioned crates to have expected and reliable outcome when upgrading. Depending on a revision/tag/branch/hash means you solve it right now but everything else must be carefully looked for, while when you update a dependency from 0.38.0 to 0.38.1 you know nothing had changed except for one or more bug fixes.

By the way, I suggest releasing a 1.0 as well, as sdl2 is in the maintenance mode now and nothing will be added to it anyway, so if this crate is almost there, I think we can go with 1.0.

@Cobrand
Copy link
Copy Markdown
Member

Cobrand commented Dec 16, 2025

I will branch from 0.38 and add this fix this week as 0.38.1, maybe a few others fixes as well if they are important as well (I haven't checked in a while).

@iddm
Copy link
Copy Markdown
Contributor

iddm commented Dec 16, 2025

I will branch from 0.38 and add this fix this week as 0.38.1, maybe a few others fixes as well if they are important as well (I haven't checked in a while).

Thanks! This one and the one with the controller reopen crash would be nice. But the latter, I guess, can't be cherry-picked that easy as it requires the fix from the C part of sdl, right?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants