-
Notifications
You must be signed in to change notification settings - Fork 0
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
Improve error "NAs are not allowed in subscripted assignments" in replacement functions #21
Comments
@moodymudskipper pinging for opinions. |
It's consistent with replace, and to me seems like the right behavior but we could override the error message with a better one. |
On a second thought - maybe this also should be left for possible future adjustments. We are close to having a first workable version, so no need to complicate things further until then... |
The translation of the first error is something like this :
Your english is better than mine so maybe you'll have a better wording |
It wouldn't be that bad to make this warning fail though... As much as I like consistency with base, I think this is never useful, you can have a script running for 20 min, only to spit when it will crash a collection of these warnings, with an intimidating "type warnings() to see the first 50". Maybe better cut it at the source. |
I was working with examples in the help files and stumbled upon this by accident:
This is of course a non-intended usage. But it's a bit unintuitive to receive this message. More so because if
x
didn't have missing values - it would work:The text was updated successfully, but these errors were encountered: