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
returned column class wrong #599
Comments
For now, work around this by using the right NA: |
@romainfrancois any thoughts on this problem? |
Hum. That This is particularly a problem because of I think I can handle the |
Alright, I put this in place. Now instead of deciding based on the first evaluation, we decide based on the first evaluation that is not NA.
|
Now is this a problem :
i.e. the first eval governs the return type, so we get It's fine in the other direction, but we lose something in this direction. options:
@hadley ? |
@romainfrancois error message sounds good to me. We should probably expand on this in a vignette somewhere. |
Given some simple data:
and a simple function:
Now apply to data:
The problem is that the first column becomes boolean instead of numeric. I think this is because the first returned result is
NA
as it works OK for the second column that also has anNA
but it appears further down...All the best
David
The text was updated successfully, but these errors were encountered: