-
Notifications
You must be signed in to change notification settings - Fork 66
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
Use chained errors in subscript checks #1735
base: main
Are you sure you want to change the base?
Conversation
2b0a03b
to
6550fd6
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I started reviewing this overall it seems like quite a lot of work for a results that's feels to me like a net neutral (or even a slight decline, since most of the errors now need extra line). So I think I must be missing some context or motivation.
@@ -218,8 +218,9 @@ | |||
Output | |||
<error/vctrs_error_subscript_type> | |||
Error in `my_function()`: | |||
! Must subset elements with a valid subscript vector. | |||
x Can't convert from `my_arg` <double> to <integer> due to loss of precision. | |||
! Can't subset elements with `my_arg`. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What does the chaining buy us here? Couldn't this be:
! Can't subset elements with `my_arg`.
i Can't convert from <double> to <integer> due to loss of precision.
No description provided.