-
Notifications
You must be signed in to change notification settings - Fork 293
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
Finish implementing vctrs methods for sfc
vectors
#1196
Conversation
057e5ba
to
5466bef
Compare
Should we move the vctrs methods into their own file I'm now looking into other data types, it might make the source more easily browsable to keep the vctrs methods separate as we might end up with a non-trivial amount of those. |
Yes, good idea! |
hmm, last Travis build failed when it shouldn't have:
This is because dev rlang and dev vctrs are temporarily in incompatible state. Is it intended that Travis checks against dev rlang and dev vctrs? I was assuming we'd be testing against CRAN versions. |
It seems because some Lines 19 to 24 in fe70fea
|
Reported in r-lib/roxygen2#979
Old habits die hard
Following up on #1172 (comment), the CRS and precision attributes are now combined. I took the conservative approach of throwing an error if they are inconsistent. This can be changed to something more appropriate by modifying |
Looks good -- thanks so much! |
Restore
n_empty
,crs
, andprecision
attributes.Add common type implementation for
sfc
objects. This finds the common class based on heuristics found inc.sfc()
.Added a new
vctrs
help topic, so that argument names can be documented separately from the tidyverse ones.