Mads Marquart

Hmm, I'm not that familiar with voice control, but this should be doable with IME. I have no plans to implement it myself, but would accept a PR that does....

Thanks for submitting the issue and both PRs, I prefer the solution in https://github.com/rust-windowing/winit/pull/3961.

I've now gone through my own FIXMEs, and opened PRs against `rustc` to fix the discrepancies I saw when trying to parse the target information. - https://github.com/rust-lang/rust/issues/131172 - https://github.com/rust-lang/rust/issues/131165 -...

I've implemented the approach discussed in https://github.com/rust-lang/cc-rs/pull/1225#discussion_r1781935441 now.

Actually, I think my biggest issue is the ad-hoc parsing of the target triple; ideally, that would be done first thing inside `Build::try_compile` as a completely separate step, and the...

Hmm, I realized that `target-lexicon` has a build script to determine the host architecture, which would probably be a bit too expensive :/ (mostly in terms of "sequential" delay, Cargo...

I lean towards thinking that https://github.com/rust-lang/cc-rs/pull/1403 was a mistake, see also discussion in https://github.com/rust-lang/cc-rs/issues/1469. This will need changes in Rust's `bootstrap` to not regress certain things there IIRC.

No wait, sorry, I lean towards https://github.com/rust-lang/cc-rs/pull/1401 being wrong. I think https://github.com/rust-lang/cc-rs/pull/1403 is the correct choice (at least for build scripts). The user's environment _should_ override whatever the build script...

> Would prefer if it just printed some platform-generic info like width, height, current state, etc instead of platform-specific info. Would probably be more parsable and helpful for users. I...

Mind if I suggest you include https://github.com/RustAudio/rodio/pull/754 in this release as well?