Use AsRef<Path> for paths#6
Merged
Merged
Conversation
Users of the API can use &str, &Path, PathBuf etc. instead of only UTF8 strings.
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Thank you for building the
mrccrate! I stumbled over the use of&strfor paths - this is a bit inconvenient, as in general, paths can be non-UTF8, so having to callPath::to_str()introduces a point of failure.With this change, users of the API can use
&str,&Path,PathBufetc. instead of only UTF8-valid strings.Some examples.