-
Notifications
You must be signed in to change notification settings - Fork 24
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Use maybe_lossy_cast() #68
Comments
Now |
@lionel-: Are you planning substantial changes to |
I would say this is a more experimental area of vctrs. It doesn't seem to be very useful either. Do you really need this? I would avoid throwing lossy cast conditions and just throw coercion errors personally. That said if you really need it go ahead, there are no changes planned now (but vctrs is not under active dev at the moment). |
- `vec_cast()` and `as_hms()` throw error instead of a warning if input can't be parsed (#68).
Thanks, throwing an error now. |
This old thread has been automatically locked. If you think you have found something related to this, please open a new issue and link to this old issue if necessary. |
in
vec_cast.hms.character()
as soon as it becomes available.The text was updated successfully, but these errors were encountered: