-
Notifications
You must be signed in to change notification settings - Fork 19
Replace ispathtype and string constructor with tryparse
#82
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
Conversation
Codecov Report
@@ Coverage Diff @@
## master #82 +/- ##
==========================================
- Coverage 91.34% 87.40% -3.95%
==========================================
Files 12 12
Lines 959 1032 +73
==========================================
+ Hits 876 902 +26
- Misses 83 130 +47
Continue to review full report at Codecov.
|
Co-Authored-By: Lyndon White <oxinabox@ucc.asn.au>
|
@oxinabox Does this seem like an appropriate use of |
|
My initial (incorrect) instinct is, "o, parse should be for thigns that are valid julia literals". It aligns with the following methods: The ones it doesn't are: |
|
Yeah, I was mostly thinking of |
You can, but i think it is clear you do have it right |
…tring construct which calls parse.
Closes #79 and #78