Remove use of target-lexicon #218
Merged
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
fitzgen
approved these changes
May 7, 2020
Avoiding target-lexicon in the public API means that dependency management for users of this crate is simpler. A breaking change in target-lexicon no longer means that this crate has to be updated first. Reducing the number of dependencies is also desirable for some users (e.g. backtrace-rs).
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.
Avoiding target-lexicon in the public API means that dependency
management for users of this crate is simpler. A breaking change
in target-lexicon no longer means that this crate has to be
updated first.
Reducing the number of dependencies is also desirable for some
users (e.g. backtrace-rs).