[T]he x86_64-apple-darwin target moves to Tier-2 due to Apple and GitHub reducing x86_64 macOS support
What does that mean? How can GitHub reduce x86_64 support in Rust?
[T]he x86_64-apple-darwin target moves to Tier-2 due to Apple and GitHub reducing x86_64 macOS support
What does that mean? How can GitHub reduce x86_64 support in Rust?
Seems to be justification according to their changelog. (Wish the site would just link to that) I'm assuming they were going to do it, anyway, now that Apple has pretty much phased out x86 support, and Github's discontinuation was just kinda put the final nail in the coffin.
Yeah, feels a little bit early when I know some devs in my company that still have x86 Macbooks, but I guess, it's not like bugs will show up immediately, so we'll see how that goes...
https://doc.rust-lang.org/nightly/rustc/platform-support.html
Tier 1 targets can be thought of as "guaranteed to work". The Rust project builds official binary releases for each tier 1 target, and automated testing ensures that each tier 1 target builds and passes tests after each change.
https://doc.rust-lang.org/nightly/rustc/target-tier-policy.html#tier-1-target-policy
The target must build and pass tests reliably in CI, for all components that Rust's CI considers mandatory.
Github is removing support for CI on that target, and since that's a requirement for Tier 1 support the target has to be downgraded.
Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!
Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.
Hope you enjoy the instance!
Rules
Follow the wormhole through a path of communities !webdev@programming.dev