Use new dependency resolver for template contract #325
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
HCastano
changed the title
cmichi
reviewed
Aug 11, 2021
cmichi
approved these changes
Aug 11, 2021
Co-authored-by: Michael Müller <michi@parity.io>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
By default, Cargo's dependency resolver leaks
stdfeatures fromdev-dependenciesintono_stdbuilds. This results in confusing errors messages such as the one inuse-ink/ink#889.
To avoid issues like this we can use the new(ish) dependency resolver, which doesn't leak
features from
dev-dependenciesinto the regular build. You can read more about it here.