Add $scalar->path to turn make a Path::Tiny object from $scalar. #247
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.
For #229
This is a very basic implementation. There's lots we can add to Path::Tiny which can come later.
The load time of Path::Tiny is up to 25% of perl5i, so we must load it
on demand.
I benchmarked the cost of "require Path::Tiny" every time and it
came out to be a significant difference for object construction.
The docs are very understated for what impact on the ease of
file manipulation this has.
Path::Tiny has some useful class methods. cwd, rootdir, tempfile
and tempdir. There's no way to access them through perl5i, you
have to use Path::Tiny directly. This is less than ideal, but
ok for now.