-
Notifications
You must be signed in to change notification settings - Fork 12
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Question] what is the reason that "AsRef<str>" is used as input instead of "AsRef<Path>"? #15
Comments
Ping @netvl If this is some functionality you could imagine being added to the library, I would go ahead and create a PR for this :) It would obviously need to be a separate function. Something like |
…tead add a module named "with_path" add function "with_path::tilde_with_context" that uses Paths instead "with_path::tilde" that uses Paths instead fixes netvl#15
Hi. As discussed in #17 I am taking over maintenance of this crate. The new repository is here: https://gitlab.com/ijackson/rust-shellexpand I agree that supporting |
closing in favor of https://gitlab.com/ijackson/rust-shellexpand/-/issues/2 |
like the title says, why is it that all function require the input to be
AsRef<str>
and notAsRef<Path>
? this means that when you have a inputPath
/PathBuf
, you would have to first convert it to a UTF8 valid string, which could invalidate the input pathThe text was updated successfully, but these errors were encountered: