-
Notifications
You must be signed in to change notification settings - Fork 2.6k
Edition key should be per-target, not per-package #5816
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Conversation
r? @matklad (rust_highfive has picked a reviewer for you, use r? to override) |
Nice! I think the test for the feature being enabled here is similar to the main feature gate for the edition key, basically only activate it if the edition specified is |
Oh also, can the documentation be updated too? |
Test: * enabling edition feature & setting at target level (happy path) * overriding the package-level edition with per-target edition * feature gating of per-target edition * per-target edition usage for rustdoc
📌 Commit 67c52ff has been approved by |
Edition key should be per-target, not per-package Fixes #5661 I've pushed this WIP PR as I'd love some early feedback on it and some tips on: * how to best to make it fail if edition is set on a target, but the feature isn't set; and * what tests this should include (i.e how exhaustive should I go) Thanks!
☀️ Test successful - status-appveyor, status-travis |
Some fingerprint cleanup. Just a minor cleanup. Move `CARGO_PKG_*` values from Metadata to Fingerprint (added in #3857). Closes #6208. This prevents stale artifacts from being left behind when these values change. Also tracks changes to the "repository" value (added in #6096). Remove `edition` as a separate field. It is already tracked in `target`. This was required previously to #5816 which added per-target editions. Also adds a helper to the testsuite to make globbing easier.
Fixes #5661
I've pushed this WIP PR as I'd love some early feedback on it and some tips on:
Thanks!