Open ericphanson opened 3 years ago
Yeah, I'll take another look that this. There is the FilePaths.@compat
macro, but depending on the use case it can often introduces ambiguities. I'm a little nervous about introducing automatic conversion for some methods if it'll introduce ambiguities on others. Seems like that kind of inconsistency is worse than doing nothing at all.
This comes up when users try things like
cp("~/my_file", S3Path("..."))
. Since often users first encouter the filepaths system via special paths likeS3Path
s, they don't realize they need to fully "opt-in" to the ecosystem by wrapping the first argument inPath
. (In other words: folks probably have not even doneusing FilePathsBase
and might not realize there is a parallel path system). I think adding methods that wrapAbstractString
arguments inPath
would help ease interoperability.