You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 28, 2022. It is now read-only.
Previously, the feature main/feat -> main/dep was activated unconditionally. This did not match Cargo's behavior, which only activated main/feat -> main/dep if dep was already active.
With guppy 0.13, guppy now matches Cargo's behavior.
This also causes a minor behavior change to hakari (#586).
The text was updated successfully, but these errors were encountered:
There was a slight issue with the way we were handling inactive,
optional dependencies. This PR should fix that.
Also expand the inside-outside tests to cover both the v1 and v2
resolvers; requires copying the fixture into a temp dir so that the
'resolver = "1"' or "2" can be added to it.
hakari output changes slightly -- this is a bugfix so it's a
non-breaking change.
See the comments in this PR for more.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
This issue tracks the Cargo build simulation fix for inactive, optional dependencies in guppy 0.13 (commit e03f119).
More about this:
Previously, the feature
main/feat
->main/dep
was activated unconditionally. This did not match Cargo's behavior, which only activatedmain/feat
->main/dep
ifdep
was already active.With guppy 0.13, guppy now matches Cargo's behavior.
This also causes a minor behavior change to hakari (#586).
The text was updated successfully, but these errors were encountered: