Skip to content
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.

Sign up for GitHub

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

Jump to bottom

map_chr implicit coercion #633

Closed
grayskripko opened this issue Feb 4, 2019 · 4 comments
Closed

map_chr implicit coercion #633

grayskripko opened this issue Feb 4, 2019 · 4 comments
Labels
bug an unexpected problem or unintended behavior map 🗺️ vctrs ♣️
Milestone
vctrs

Comments

@grayskripko
Copy link

Why it isn't so strict to throw an error?

1:2 %>% map_chr(length)
# > [1] "1" "1"
@lionel-
Copy link
Member

lionel- commented Feb 27, 2019

This will change when we switch to vctrs for our coercion backend.

@lionel- lionel- added this to the vctrs milestone Feb 27, 2019
@grayskripko
Copy link
Author

ok. Do you need this issue open?

@lionel-
Copy link
Member

lionel- commented Feb 27, 2019

Yes we'll tackle it at the vctrs milestone.

@DavisVaughan DavisVaughan mentioned this issue Jun 18, 2019
Closed
2 tasks
@hadley hadley added the bug an unexpected problem or unintended behavior label Aug 27, 2022
@hadley
Copy link
Member

hadley commented Aug 30, 2022

Now tracking in #904

@hadley hadley closed this as completed Aug 30, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug an unexpected problem or unintended behavior map 🗺️ vctrs ♣️
Projects
None yet
Milestone
vctrs
Development

No branches or pull requests
3 participants
@hadley @lionel- @grayskripko